Skip to main content
Glama
webflow

Webflow

Official
by webflow

Delete Collection Item

collections_items_delete_item

Delete a specific item from a Webflow CMS collection by providing the collection ID and item ID. Optionally specify a locale ID to delete from non-primary locales.

Instructions

Delete an item in a CMS collection. Items will only be deleted in the primary locale unless a cmsLocaleId is included in the request.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
collection_idYesUnique identifier for the Collection.
itemIdYesItem ID to be deleted.
cmsLocaleIdsNoUnique identifier for the locale of the CMS Item.

Implementation Reference

  • Handler function that deletes a CMS collection item by calling the Webflow API's deleteItem method.
    async ({ collection_id, itemId, cmsLocaleIds }) => {
      try {
        const response = await getClient().collections.items.deleteItem(
          collection_id,
          itemId,
          { cmsLocaleId: cmsLocaleIds },
          requestOptions
        );
        return formatResponse(JSON.stringify("Item deleted"));
      } catch (error) {
        return formatErrorResponse(error);
      }
    }
  • Zod input schema defining parameters for the delete item tool: collection_id, itemId, and optional cmsLocaleIds.
    inputSchema: z.object({
      collection_id: z
        .string()
        .describe("Unique identifier for the Collection."),
      itemId: z.string().describe("Item ID to be deleted."),
      cmsLocaleIds: z
        .string()
        .optional()
        .describe("Unique identifier for the locale of the CMS Item."),
    }),
  • Tool registration call for 'collections_items_delete_item' including schema, description, and inline handler.
    server.registerTool(
      "collections_items_delete_item",
      {
        title: "Delete Collection Item",
        description:
          "Delete an item in a CMS collection. Items will only be deleted in the primary locale unless a cmsLocaleId is included in the request. ",
        inputSchema: z.object({
          collection_id: z
            .string()
            .describe("Unique identifier for the Collection."),
          itemId: z.string().describe("Item ID to be deleted."),
          cmsLocaleIds: z
            .string()
            .optional()
            .describe("Unique identifier for the locale of the CMS Item."),
        }),
      },
      async ({ collection_id, itemId, cmsLocaleIds }) => {
        try {
          const response = await getClient().collections.items.deleteItem(
            collection_id,
            itemId,
            { cmsLocaleId: cmsLocaleIds },
            requestOptions
          );
          return formatResponse(JSON.stringify("Item deleted"));
        } catch (error) {
          return formatErrorResponse(error);
        }
      }
    );
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 mentions locale-specific deletion behavior, which is useful, but fails to disclose critical traits like whether deletion is permanent, requires specific permissions, or has rate limits. For a destructive tool with zero annotation coverage, this is a significant gap in transparency.

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 efficiently structured in two sentences, with the first stating the core action and the second adding crucial locale-related nuance. There's no wasted language, and it's front-loaded with the primary purpose, though it could be slightly more polished for a perfect score.

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 this is a destructive tool with no annotations and no output schema, the description is incomplete. It lacks information on permissions, irreversible effects, error handling, or response format, which are critical for safe agent invocation. The locale detail is helpful but insufficient for full contextual understanding.

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 all three parameters ('collection_id', 'itemId', 'cmsLocaleIds') with clear descriptions. The description adds minimal value by hinting at the optional 'cmsLocaleIds' parameter's effect on locale behavior, but doesn't provide additional syntax or format details beyond what the schema offers, justifying a baseline score.

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 ('Delete') and resource ('an item in a CMS collection'), making the purpose immediately understandable. It distinguishes from siblings like 'collections_items_update_items' by specifying deletion rather than modification. However, it doesn't explicitly contrast with 'collections_items_publish_items' or other destructive operations, keeping it from a perfect score.

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 by mentioning locale behavior ('only deleted in the primary locale unless a cmsLocaleId is included'), which provides some context for when to use this tool. However, it doesn't explicitly state when to use it versus alternatives like 'collections_items_update_items' for modifications or warn about irreversible deletion, leaving guidance incomplete.

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