Skip to main content
Glama
webflow

Webflow

Official
by webflow

List Pages

pages_list

Retrieve all pages from a Webflow site with metadata including IDs, titles, and slugs for site management and navigation.

Instructions

List all pages within a site. Returns page metadata including IDs, titles, and slugs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
site_idYesThe site's unique ID, used to list its pages.
localeIdNoUnique identifier for a specific locale. Applicable when using localization.
limitNoMaximum number of records to be returned (max limit: 100)
offsetNoOffset used for pagination if the results have more than limit records.

Implementation Reference

  • The handler function that implements the pages_list tool logic by calling Webflow API to list pages for a given site.
    async ({ site_id, localeId, limit, offset }) => {
      try {
        const response = await getClient().pages.list(
          site_id,
          {
            localeId,
            limit,
            offset,
          },
          requestOptions
        );
        return formatResponse(response);
      } catch (error) {
        return formatErrorResponse(error);
      }
    }
  • Zod input schema defining parameters for the pages_list tool: site_id (required), localeId, limit, offset (optional).
    inputSchema: z.object({
      site_id: z
        .string()
        .describe("The site's unique ID, used to list its pages."),
      localeId: z
        .string()
        .optional()
        .describe(
          "Unique identifier for a specific locale. Applicable when using localization."
        ),
      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."
        ),
    }),
  • Full registration of the pages_list tool on the MCP server within registerPagesTools function.
    server.registerTool(
      "pages_list",
      {
        title: "List Pages",
        description:
          "List all pages within a site. Returns page metadata including IDs, titles, and slugs.",
        inputSchema: z.object({
          site_id: z
            .string()
            .describe("The site's unique ID, used to list its pages."),
          localeId: z
            .string()
            .optional()
            .describe(
              "Unique identifier for a specific locale. Applicable when using localization."
            ),
          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."
            ),
        }),
      },
      async ({ site_id, localeId, limit, offset }) => {
        try {
          const response = await getClient().pages.list(
            site_id,
            {
              localeId,
              limit,
              offset,
            },
            requestOptions
          );
          return formatResponse(response);
        } catch (error) {
          return formatErrorResponse(error);
        }
      }
    );
  • src/mcp.ts:51-51 (registration)
    Invocation of registerPagesTools during overall tool registration, which includes pages_list.
    registerPagesTools(server, getClient);
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 the return format ('page metadata including IDs, titles, and slugs') but lacks critical details like pagination behavior (implied by limit/offset parameters but not explained), rate limits, authentication requirements, or error conditions. For a list operation with pagination parameters, this is insufficient.

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 two concise sentences with zero waste. The first sentence states the action and scope, the second describes the return format. It's appropriately sized and front-loaded with essential information.

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 list tool with 4 parameters, 100% schema coverage, but no annotations and no output schema, the description is minimally adequate. It covers purpose and return format but lacks behavioral context (pagination, errors, auth) and usage guidance. The absence of output schema means the description should ideally explain the return structure more thoroughly.

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 fully documents all four parameters. The description adds no additional parameter semantics beyond what's in the schema (e.g., it doesn't clarify relationships between parameters like how localeId affects results). Baseline 3 is appropriate when schema does the heavy lifting.

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 verb ('List') and resource ('pages within a site'), and specifies the scope ('all pages'). It distinguishes from sibling tools like 'pages_get_content' and 'pages_get_metadata' by focusing on listing rather than retrieving specific content or metadata.

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 like 'pages_get_content' or 'pages_get_metadata'. It doesn't mention prerequisites, exclusions, or comparative use cases with sibling tools, leaving the agent to infer usage context.

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