Webflow MCP Server

collections_items_publish_items

Publish draft items in a Webflow CMS collection to make them live. Provide collection ID and item IDs to update status.

Instructions

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

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "collection_id": "<collection_id>",
      "itemIds": "<itemIds>"
    },
    "name": "collections_items_publish_items"
  }
}

Input Schema

Name	Required	Description	Default
`itemIds`	Yes	Array of item IDs to be published.
`collection_id`	Yes	Unique identifier for the Collection.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.7.0Aug 9, 2026

TDQS

B3.3/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the core action but omits important details such as permission requirements, reversibility, idempotency, or response format. The phrase 'make them live' conveys the transition but little else.

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 sentence that communicates the action and result without unnecessary words. It is well-structured and front-loaded with the verb.

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

Completeness3/5

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

For a simple two-parameter mutation tool, the description covers the basic action, but it lacks usage guidance and behavioral context. Since there is no output schema and no annotations, the description could do more to explain expected outcomes, prerequisites, and edge cases. However, the schema fills in parameter details, so the description is minimally complete.

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?

The input schema already provides complete descriptions for both parameters (collection_id and itemIds), covering 100% of the parameters. The description adds no extra parameter-level syntax or constraints beyond what the schema provides, so it meets the baseline but does not exceed it.

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

Purpose5/5

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

The description uses the specific verb 'Publish' and clearly identifies both the resource ('draft items in a CMS collection') and the outcome ('make them live'). This distinguishes it from sibling tools like create_item_live or update_items_live, which operate on live items directly.

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 choose this tool over alternatives such as collections_items_create_item_live or sites_publish. It lacks any prerequisites, exclusions, or alternative tool names.

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