Webflow MCP Server

collections_items_create_item

Create new draft items in a Webflow CMS collection by providing the collection ID and item field data.

Instructions

Create new items in a CMS collection as drafts.

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>",
      "request": "<request>"
    },
    "name": "collections_items_create_item"
  }
}

Input Schema

Name	Required	Description	Default
`request`	Yes
`collection_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.7.0Aug 9, 2026

TDQS

B3.2/5.0

Behavior3/5

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

There are no annotations, so the description carries the full burden. It does disclose a key behavioral trait—items are created as drafts, not published—which is useful context. However, it does not mention permissions, reversibility, validation requirements, or return behavior, leaving significant gaps for a mutation tool.

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, front-loaded sentence with no wasted words. It states the core action and the draft state clearly. It is concise, though perhaps too brief to cover necessary detail—but that lack is captured by other dimensions.

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 nested parameter schema and no output schema or annotations, the description is critically incomplete. It offers no explanation of required fields, item structure, or expected behavior beyond the draft status. A tool with this complexity needs far more context for correct invocation.

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

Parameters1/5

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

Schema description coverage is 0%, and the description provides no parameter guidance. It does not explain what collection_id refers to, nor the structure of request, items, or fieldData. The nested schema with required fields (name, slug) is completely unaddressed, failing to help the agent construct a valid request.

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 clearly states the tool's function: creating new items in a CMS collection, specifically as drafts. The verb 'create' is specific, the resource is identified ('items in a CMS collection'), and the draft qualifier distinguishes it from the sibling tool collections_items_create_item_live.

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

Usage Guidelines3/5

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

The description implies use for draft creation via 'as drafts', but does not explicitly mention when to use this tool versus alternatives (e.g., collections_items_create_item_live). No exclusions or conditions are stated, leaving the distinction implicit rather than explicit.

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