Skip to main content
Glama
webflow

Webflow

Official
by webflow

List Collection Items

collections_items_list_items

Retrieve CMS collection items with filtering, sorting, and pagination options to manage content efficiently.

Instructions

List items in a CMS collection with optional filtering and sorting.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
collection_idYesUnique identifier for the Collection.
cmsLocaleIdNoUnique identifier for the locale of the CMS Item.
limitNoMaximum number of records to be returned (max limit: 100)
offsetNoOffset used for pagination if the results have more than limit records.
nameNoName of the field.
slugNoURL structure of the Item in your site. Note: Updates to an item slug will break all links referencing the old slug.
sortByNoField to sort the items by. Allowed values: lastPublished, name, slug.
sortOrderNoOrder to sort the items by. Allowed values: asc, desc.

Implementation Reference

  • Registers the 'collections_items_list_items' MCP tool, defining its input schema, title, description, and handler function.
    server.registerTool(
      "collections_items_list_items",
      {
        title: "List Collection Items",
        description:
          "List items in a CMS collection with optional filtering and sorting.",
        inputSchema: z.object({
          collection_id: z
            .string()
            .describe("Unique identifier for the Collection."),
          cmsLocaleId: z
            .string()
            .optional()
            .describe("Unique identifier for the locale of the CMS Item."),
          limit: z
            .number()
            .optional()
            .describe(
              "Maximum number of records to be returned (max limit: 100)"
            ),
          offset: z
            .number()
            .optional()
            .describe(
              "Offset used for pagination if the results have more than limit records."
            ),
          name: z.string().optional().describe("Name of the field."),
          slug: z
            .string()
            .optional()
            .describe(
              "URL structure of the Item in your site. Note: Updates to an item slug will break all links referencing the old slug."
            ),
          sortBy: WebflowCollectionsItemsListItemsRequestSortBySchema,
          sortOrder: WebflowCollectionsItemsListItemsRequestSortOrderSchema,
        }),
      },
      async ({
        collection_id,
        cmsLocaleId,
        offset,
        limit,
        name,
        slug,
        sortBy,
        sortOrder,
      }) => {
        try {
          const response = await getClient().collections.items.listItems(
            collection_id,
            {
              cmsLocaleId,
              offset,
              limit,
              name,
              slug,
              sortBy,
              sortOrder,
            },
            requestOptions
          );
          return formatResponse(response);
        } catch (error) {
          return formatErrorResponse(error);
        }
      }
    );
  • The handler function that invokes the Webflow API to list items in a collection with provided filters, sorting, and pagination.
    async ({
      collection_id,
      cmsLocaleId,
      offset,
      limit,
      name,
      slug,
      sortBy,
      sortOrder,
    }) => {
      try {
        const response = await getClient().collections.items.listItems(
          collection_id,
          {
            cmsLocaleId,
            offset,
            limit,
            name,
            slug,
            sortBy,
            sortOrder,
          },
          requestOptions
        );
        return formatResponse(response);
      } catch (error) {
        return formatErrorResponse(error);
      }
    }
  • Zod schema defining the allowed sort order values ('asc', 'desc') for the tool input.
    export const WebflowCollectionsItemsListItemsRequestSortOrderSchema = z
      .enum(["asc", "desc"])
      .optional()
      .describe("Order to sort the items by. Allowed values: asc, desc.");
  • Zod schema defining the allowed sort by fields ('lastPublished', 'name', 'slug') for the tool input.
    export const WebflowCollectionsItemsListItemsRequestSortBySchema = z
      .enum(["lastPublished", "name", "slug"])
      .optional()
      .describe(
        "Field to sort the items by. Allowed values: lastPublished, name, slug."
      );
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions filtering and sorting capabilities but doesn't describe important behavioral aspects like pagination behavior (implied by limit/offset but not explained), rate limits, authentication requirements, whether it's read-only or has side effects, or what format the returned items will have. The description is too minimal for a tool with 8 parameters.

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 extremely concise - a single sentence that communicates the core purpose efficiently. There's no wasted language or unnecessary elaboration, making it easy to parse and understand quickly.

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 tool with 8 parameters, no annotations, and no output schema, the description is insufficiently complete. It doesn't explain what the tool returns, how results are structured, pagination behavior, or important constraints. While the schema documents parameters well, the overall context for using this tool effectively is lacking.

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 description mentions 'optional filtering and sorting' which hints at some parameters, but with 100% schema description coverage, all parameters are already well-documented in the schema. The description adds minimal value beyond what's in the structured schema, meeting the baseline for high schema coverage.

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 ('List items') and resource ('in a CMS collection'), making the purpose immediately understandable. It distinguishes from some siblings like 'collections_list' (which lists collections rather than items) but doesn't explicitly differentiate from other item-related tools like 'collections_items_create_item' or 'collections_items_update_items'.

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 use this tool versus alternatives. It mentions 'optional filtering and sorting' but doesn't indicate when filtering is appropriate, what alternatives exist for similar operations, or any prerequisites beyond the required collection_id parameter.

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