/bulk-cms-update

name: webflow-mcp:bulk-cms-update
description: Create or update multiple CMS items in a Webflow collection with validation and diff preview. Use when adding multiple blog posts, products, or updating fields across many items.

Bulk CMS Update

Create or update multiple CMS items with comprehensive validation, granular approval, and rollback capability.

Important Note

**ALWAYS use Webflow MCP tools for all operations:**

• Use Webflow MCP's `data_sites_tool` with action `list_sites` for listing available sites
• Use Webflow MCP's `data_cms_tool` with action `get_collection_list` for listing CMS collections
• Use Webflow MCP's `data_cms_tool` with action `get_collection_details` for fetching collection schemas
• Use Webflow MCP's `data_cms_tool` with action `list_collection_items` for retrieving existing items
• Use Webflow MCP's `data_cms_tool` with action `create_collection_items` for creating items (draft or published)
• Use Webflow MCP's `data_cms_tool` with action `update_collection_items` for updating items (draft or published)
• Use Webflow MCP's `data_cms_tool` with action `publish_collection_items` for publishing draft items
• Use Webflow MCP's `webflow_guide_tool` to get best practices before starting
• DO NOT use any other tools or methods for Webflow operations
• All tool calls must include the required `context` parameter (15-25 words, third-person perspective)

Instructions

Phase 1: Site & Collection Selection

1. **Get site**: Identify the target site. If user does not provide site ID, ask for it. 2. **List collections**: Use Webflow MCP's `data_cms_tool` with action `get_collection_list` to show available collections 3. **Ask user to select collection**: User specifies which collection to work with 4. **Fetch collection schema**: Use Webflow MCP's `data_cms_tool` with action `get_collection_details` to retrieve:

• All field definitions with types
• Required vs optional fields
• Field validations (max length, patterns, etc.)
• Reference field targets

Phase 2: Data Collection & Parsing

5. **Ask operation type**: Clarify what user wants to do:

• Create new items only
• Update existing items only
• Both create and update

6. **Receive data from user**: Accept data in flexible formats:

• Structured format (JSON-like)
• Natural language descriptions
• CSV-style data
• Bullet lists

7. **Parse and normalize**: Convert user data into structured format 8. **Fetch existing items** (if updates involved): Use Webflow MCP's `data_cms_tool` with action `list_collection_items` to get current data

**IMPORTANT - Efficient Item Lookup:**

• When searching for specific items by name, ALWAYS use the `name` parameter to filter (e.g., `name: "Pikachu"`)
• When searching by slug, use the `slug` parameter to filter
• NEVER fetch all items first and then search through the results - this wastes API calls and tokens
• Only fetch the full list when you need to display all items or don't know which specific items to target

Phase 3: Validation & Analysis

9. **Validate all data**:

• **Field names**: Check all field names exist in schema
• **Required fields**: Ensure all required fields are provided
• **Field types**: Validate data types match schema
• **Constraints**: Check max lengths, patterns, allowed values
• **Slugs**: Ensure slugs are unique and valid
• **Reference fields**: Verify referenced items exist

10. **Detect conflicts**:

• Duplicate slugs (within batch or with existing items)
• Missing required fields
• Invalid data types
• Constraint violations

11. **Analyze impact**:

• Count creates vs updates
• Identify which fields will change
• Calculate batch size and processing time

Phase 4: Preview & Granular Approval

12. **Generate detailed preview**:

• Show each item with validation status
• Display warnings for any issues
• For updates, show diffs (old → new)
• For creates, show all field values
• Number each item for selective approval

13. **Present granular approval options**:

• Allow user to select specific items to process
• Options: "all", "none", specific numbers, number ranges
• Show estimated processing time

14. **Offer publish options**:

• Publish immediately (use `*_live` endpoints)
• Create as drafts (use regular endpoints + manual publish)

Phase 5: Execution & Reporting

15. **Store rollback data**: Before any changes, save:

• Original values for all updated items
• Timestamp
• Operation details

16. **Process in batches**:

• Maximum 50 items per batch
• Show progress indicator
• Handle rate limits gracefully

17. **Execute operations**: Use appropriate Webflow MCP tools based on user choice 18. **Handle errors gracefully**:

• Continue processing on single item failures
• Track successes and failures separately
• Provide detailed error messages

19. **Generate comprehensive report**:

• Summary (success/failure counts)
• Detailed results per item
• Item IDs for created/updated items
• Error details for failed items

20. **Offer rollback option**: Allow user to undo changes if needed

Examples

**User prompt:**

Add 2 blog posts about Webflow MCP and update the first blog to say "Top" instead of "Best"

**Step 1: Site & Collection Selection**

📋 Bulk CMS Update Setup

Available Sites:
1. MCP Demo#1
2. MCP Demo#2
3. MCP Demo#3

Please select a site (1-3):

*User selects: 1*

Available Collections in MCP Demo#1:
└── Blog Posts (9 items)
    Fields: name, slug, post-body, post-summary, main-image, thumbnail-image, featured, color

Proceed with Blog Posts collection? (yes/no)

*User confirms: yes*

**Step 2: Data Collection**

🔍 Collection Schema: Blog Posts

Required Fields:
- name (PlainText, max 256 chars)
- slug (PlainText, max 256 chars, alphanumeric only)

Optional Fields:
- post-body (RichText)
- post-summary (PlainText)
- main-image (I