Skip to main content
Glama
deenesjakoruzh
webflow

Webflow

Official
by webflow
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Publish Collection Items

collections_items_publish_items

Publish draft items in a Webflow CMS collection to make them live on your website. Use this tool to update content from draft to published status.

Instructions

Publish draft items in a CMS collection to make them live.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
collection_idYesUnique identifier for the Collection.
itemIdsYesArray of item IDs to be published.

Implementation Reference

  • src/tools/cms.ts:407-420 (handler)
    Handler function that executes the tool logic: publishes specified items in a CMS collection to live using the WebflowClient's publishItem method.
    async ({ collection_id, itemIds }) => {
  try {
    const response = await getClient().collections.items.publishItem(
      collection_id,
      {
        itemIds: itemIds,
      },
      requestOptions
    );
    return formatResponse(response);
  } catch (error) {
    return formatErrorResponse(error);
  }
}
  • src/tools/cms.ts:393-421 (registration)
    Registration of the 'collections_items_publish_items' MCP tool, including title, description, input schema, and inline handler.
    server.registerTool(
  "collections_items_publish_items",
  {
    title: "Publish Collection Items",
    description: "Publish draft items in a CMS collection to make them live.",
    inputSchema: z.object({
      collection_id: z
        .string()
        .describe("Unique identifier for the Collection."),
      itemIds: z
        .array(z.string())
        .describe("Array of item IDs to be published."),
    }),
  },
  async ({ collection_id, itemIds }) => {
    try {
      const response = await getClient().collections.items.publishItem(
        collection_id,
        {
          itemIds: itemIds,
        },
        requestOptions
      );
      return formatResponse(response);
    } catch (error) {
      return formatErrorResponse(error);
    }
  }
);
  • src/tools/cms.ts:398-405 (schema)
    Zod input schema defining parameters: collection_id (string) and itemIds (array of strings).
    inputSchema: z.object({
  collection_id: z
    .string()
    .describe("Unique identifier for the Collection."),
  itemIds: z
    .array(z.string())
    .describe("Array of item IDs to be published."),
}),

Tool Definition Quality

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('publish') but doesn't describe critical traits: whether this is a destructive/mutative operation, permission requirements, rate limits, error handling, or what happens to published items (e.g., irreversible changes). 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 purpose ('Publish draft items in a CMS collection') and adds a clarifying phrase ('to make them live') that reinforces the action. Every word earns its place.

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 complexity of a publishing operation (likely mutative), no annotations, and no output schema, the description is incomplete. It doesn't cover behavioral aspects like side effects, return values, or error conditions. For a tool that changes item states, 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 100%, so the schema already documents both parameters ('collection_id' and 'itemIds') with clear descriptions. The description adds no additional meaning beyond what the schema provides, such as format details or usage examples. Baseline 3 is appropriate when the schema does the heavy lifting.

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 ('publish') and resource ('draft items in a CMS collection'), specifying the action and target. It distinguishes from siblings like 'collections_items_create_item' (creation) and 'collections_items_update_items' (updating), but doesn't explicitly differentiate from 'collections_items_create_item_live' or 'sites_publish', which might have overlapping publishing functionality.

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 implies usage for making draft items live, but provides no explicit guidance on when to use this tool versus alternatives like 'collections_items_create_item_live' or 'sites_publish'. It lacks prerequisites (e.g., items must be in draft state) and doesn't mention any exclusions or specific contexts.

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