Skip to main content
Glama
webflow

Webflow

Official
by webflow

Update Collection Items

collections_items_update_items

Update existing items in Webflow CMS collections as drafts to modify content before publishing changes.

Instructions

Update existing items in a CMS collection as drafts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
collection_idYesUnique identifier for the Collection.
requestYes

Implementation Reference

  • The inline handler function for the 'collections_items_update_items' tool. It calls the Webflow API's updateItems method to update collection items as drafts and formats the response or error.
    async ({ collection_id, request }) => {
      try {
        const response = await getClient().collections.items.updateItems(
          collection_id,
          request,
          requestOptions
        );
        return formatResponse(response);
      } catch (error) {
        return formatErrorResponse(error);
      }
    }
  • Registers the 'collections_items_update_items' tool on the MCP server, specifying its title, description, input schema, and inline handler function.
      "collections_items_update_items",
      {
        title: "Update Collection Items",
        description: "Update existing items in a CMS collection as drafts.",
        inputSchema: z.object({
          collection_id: z
            .string()
            .describe("Unique identifier for the Collection."),
          request: WebflowCollectionsItemsUpdateItemsRequestSchema,
        }),
      },
      async ({ collection_id, request }) => {
        try {
          const response = await getClient().collections.items.updateItems(
            collection_id,
            request,
            requestOptions
          );
          return formatResponse(response);
        } catch (error) {
          return formatErrorResponse(error);
        }
      }
    );
  • Zod schema defining the structure of the request body for updating collection items, consisting of an optional array of items each with an ID and field data.
    export const WebflowCollectionsItemsUpdateItemsRequestSchema = z.object({
      items: z.array(CollectionItemWithIdInputSchema).optional(),
    });
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden but offers limited behavioral insight. It mentions 'as drafts' indicating non-immediate publication, but doesn't disclose critical traits like required authentication, rate limits, error handling, whether updates are reversible, or what happens to unpublished changes. For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding operational behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that front-loads the core action ('Update existing items'). There's no wasted wording, though it could be more structured with brief usage notes. Every word earns its place, making it appropriately concise for the tool's complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (mutation with nested objects, no annotations, no output schema), the description is insufficient. It doesn't address return values, error conditions, side effects, or how draft updates interact with publishing. For a CMS update operation affecting multiple items with rich schema, more context is needed to guide proper invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 50%, with parameters like 'collection_id' and nested 'request' objects documented in schema. The description adds no parameter-specific semantics beyond implying 'items' are updated as drafts. It doesn't explain the structure of 'fieldData', format of date fields, or consequences of slug updates mentioned in schema. Baseline 3 is appropriate as schema provides moderate documentation, but description doesn't compensate for coverage gaps.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('Update') and resource ('existing items in a CMS collection'), specifying the scope ('as drafts'). It distinguishes from sibling 'collections_items_update_items_live' by implying draft vs live updates, though not explicitly named. However, it doesn't fully differentiate from other update tools like 'collections_fields_update' or 'components_update_content'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides minimal guidance by specifying 'as drafts', which hints at when to use this vs 'collections_items_update_items_live'. However, it lacks explicit when-not scenarios, prerequisites (e.g., required permissions), or alternatives for related operations like creating or deleting items. No clear context for choosing this over other update tools in the sibling list.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/webflow/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server