Skip to main content
Glama
webflow

Webflow

Official
by webflow

Update Items Live

collections_items_update_items_live

Update and publish CMS collection items directly to your live Webflow site. Modify content and push changes without manual publishing steps.

Instructions

Update and publish existing items in a CMS collection directly to the live site.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
collection_idYesUnique identifier for the Collection.
requestYes

Implementation Reference

  • Registers the 'collections_items_update_items_live' MCP tool, including its input schema reference and inline async handler function. The handler calls the Webflow API to update and publish CMS collection items live.
    server.registerTool(
      "collections_items_update_items_live",
      {
        title: "Update Items Live",
        description:
          "Update and publish existing items in a CMS collection directly to the live site.",
        inputSchema: z.object({
          collection_id: z
            .string()
            .describe("Unique identifier for the Collection."),
          request: WebflowCollectionsItemsUpdateItemsLiveRequestSchema,
        }),
      },
      async ({ collection_id, request }) => {
        try {
          const response = await getClient().collections.items.updateItemsLive(
            collection_id,
            request,
            requestOptions
          );
          return formatResponse(response);
        } catch (error) {
          return formatErrorResponse(error);
        }
      }
  • Inline handler function for the tool that executes the Webflow API call to update items live in a CMS collection.
    async ({ collection_id, request }) => {
      try {
        const response = await getClient().collections.items.updateItemsLive(
          collection_id,
          request,
          requestOptions
        );
        return formatResponse(response);
      } catch (error) {
        return formatErrorResponse(error);
      }
    }
  • Zod schema defining the structure of the request for updating CMS collection items live, including items array with fields like id, fieldData, etc.
    export const WebflowCollectionsItemsUpdateItemsLiveRequestSchema = z.object({
      items: z
        .array(
          z.object({
            id: z.string(),
            cmsLocaleId: z
              .string()
              .optional()
              .describe("Unique identifier for the locale of the CMS Item."),
            lastPublished: z
              .string()
              .optional()
              .describe("Date when the item was last published."),
            lastUpdated: z
              .string()
              .optional()
              .describe("Date when the item was last updated."),
            createdOn: z
              .string()
              .optional()
              .describe("Date when the item was created."),
            isArchived: z
              .boolean()
              .optional()
              .describe("Indicates if the item is archived."),
            isDraft: z
              .boolean()
              .optional()
              .describe("Indicates if the item is a draft."),
            fieldData: z
              .record(z.any())
              .and(
                z.object({
                  name: z.string().optional().describe("Name of the field."),
                  slug: z
                    .string()
                    .optional()
                    .describe(
                      "URL structure of the Item in your site. Note: Updates to an item slug will break all links referencing the old slug."
                    ),
                })
              )
              .optional()
              .describe("Array of items to be updated."),
          })
        )
        .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 for behavioral disclosure. It mentions 'publish... directly to the live site' which implies a write operation with immediate public impact, but fails to address critical aspects like required permissions, whether changes are reversible, rate limits, error handling, or what the response looks like. For a mutation tool with zero annotation coverage, this is a significant gap.

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

Conciseness5/5

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

The description is a single, efficient sentence with zero waste—it front-loads the core action and target without unnecessary words. Every part ('Update and publish', 'existing items', 'CMS collection', 'directly to the live site') earns its place by contributing essential information.

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 immediate publishing, 2 parameters including nested objects, no annotations, no output schema), the description is inadequate. It lacks details on behavioral traits, error conditions, response format, and how it differs from siblings. For a tool that modifies and publishes content live, more context is needed to ensure safe and correct usage.

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 only 'collection_id' and 'fieldData' having descriptions. The tool description adds no parameter-specific information beyond what's in the schema—it doesn't explain the structure of 'request.items', clarify what 'update' entails, or provide examples. Since schema coverage is moderate, the description doesn't compensate enough, meeting the baseline for minimal value addition.

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 action ('Update and publish') and target ('existing items in a CMS collection directly to the live site'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'collections_items_update_items' (which likely updates without publishing) or 'collections_items_publish_items' (which likely publishes without updating), missing full sibling differentiation.

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 no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing existing items), exclusions (e.g., not for creating new items), or compare it to similar tools like 'collections_items_update_items' or 'collections_items_publish_items' from the sibling list, leaving the agent with no usage context.

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