Skip to main content
Glama
webflow

Webflow

Official
by webflow

Create Item Live

collections_items_create_item_live

Create and publish new CMS collection items directly to your live Webflow site. Add content to collections and make it immediately visible to visitors.

Instructions

Create and publish new items in a CMS collection directly to the live site.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
collection_idYesUnique identifier for the Collection.
requestYes

Implementation Reference

  • Full registration of the 'collections_items_create_item_live' tool, including name, input schema using WebflowCollectionsItemsCreateItemLiveRequestSchema, and inline handler function that calls the Webflow API to create item live.
    server.registerTool(
      "collections_items_create_item_live",
      {
        title: "Create Item Live",
        description:
          "Create and publish new items in a CMS collection directly to the live site.",
        inputSchema: z.object({
          collection_id: z
            .string()
            .describe("Unique identifier for the Collection."),
          request: WebflowCollectionsItemsCreateItemLiveRequestSchema,
        }),
      },
      async ({ collection_id, request }) => {
        try {
          const response = await getClient().collections.items.createItemLive(
            collection_id,
            request,
            requestOptions
          );
          return formatResponse(response);
        } catch (error) {
          return formatErrorResponse(error);
        }
      }
    );
  • The inline handler function for the tool that performs the actual API call to create and publish a CMS item live using the Webflow client.
    async ({ collection_id, request }) => {
      try {
        const response = await getClient().collections.items.createItemLive(
          collection_id,
          request,
          requestOptions
        );
        return formatResponse(response);
      } catch (error) {
        return formatErrorResponse(error);
      }
    }
  • Zod schema defining the input structure for the createItemLive request, including items array with fields like fieldData, name, slug, etc.
    export const WebflowCollectionsItemsCreateItemLiveRequestSchema = z.object({
      items: z
        .array(
          z.object({
            id: z.string().optional(),
            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().describe("Name of the field."),
                slug: z
                  .string()
                  .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 created."),
    });
Behavior2/5

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

With no annotations, the description carries full burden. It mentions 'publish... directly to the live site' which implies a write operation with immediate public visibility, but doesn't disclose critical behavioral traits like required permissions, whether changes are reversible, rate limits, or what happens on failure. The description is insufficient for a mutation tool with zero annotation coverage.

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 that front-loads the core purpose. Every word earns its place with no redundancy or unnecessary elaboration.

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?

For a mutation tool that publishes content live with no annotations and no output schema, the description is inadequate. It doesn't cover error conditions, response format, side effects, or important constraints like the 'slug' warning mentioned in the schema. The agent lacks sufficient context to use this tool safely and effectively.

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% (only 'collection_id' and 'items' have descriptions). The description adds no parameter-specific information beyond what's in the schema. It doesn't explain the structure of 'fieldData', required fields beyond 'name' and 'slug', or the relationship between parameters. Baseline 3 is appropriate given the partial schema coverage.

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 action ('Create and publish'), the resource ('new items in a CMS collection'), and the destination ('directly to the live site'). It distinguishes from sibling tools like 'collections_items_create_item' (which likely creates drafts) by specifying 'live' publication.

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 usage for immediate publication to live sites, but doesn't explicitly state when to use this vs. alternatives like 'collections_items_create_item' (for drafts) or 'collections_items_publish_items' (for publishing existing items). No guidance on prerequisites or exclusions is provided.

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