Skip to main content
Glama
webflow

Webflow

Official
by webflow

Get Page Content

pages_get_content

Retrieve structured content and data for a specific Webflow page, including all elements and their properties, to analyze or integrate page information.

Instructions

Get the content structure and data for a specific page including all elements and their properties.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
page_idYesUnique identifier for the page.
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

  • Registration of the 'pages_get_content' tool, including input schema, description, and handler function.
      "pages_get_content",
      {
        title: "Get Page Content",
        description:
          "Get the content structure and data for a specific page including all elements and their properties.",
        inputSchema: z.object({
          page_id: z.string().describe("Unique identifier for the page."),
          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 ({ page_id, localeId, limit, offset }) => {
        try {
          const response = await getClient().pages.getContent(
            page_id,
            {
              localeId,
              limit,
              offset,
            },
            requestOptions
          );
          return formatResponse(response);
        } catch (error) {
          return formatErrorResponse(error);
        }
      }
    );
  • The handler function that executes the tool logic by calling Webflow API to get page content.
    async ({ page_id, localeId, limit, offset }) => {
      try {
        const response = await getClient().pages.getContent(
          page_id,
          {
            localeId,
            limit,
            offset,
          },
          requestOptions
        );
        return formatResponse(response);
      } catch (error) {
        return formatErrorResponse(error);
      }
    }
  • Zod input schema defining parameters for the pages_get_content tool: page_id (required), localeId, limit, offset (optional).
    inputSchema: z.object({
      page_id: z.string().describe("Unique identifier for the page."),
      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."
        ),
    }),
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. While 'Get' implies a read-only operation, the description doesn't clarify permissions, rate limits, pagination behavior (beyond what's in the schema), or what happens with invalid inputs. For a tool with 4 parameters and no annotation coverage, this leaves significant gaps in understanding its behavior.

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, well-structured sentence that efficiently conveys the core functionality without unnecessary words. It's front-loaded with the main purpose and includes key details about scope. Every part of the sentence earns its place.

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 complexity (4 parameters, no annotations, no output schema), the description is incomplete. It doesn't explain the return format, error handling, or how pagination works with 'limit' and 'offset'. For a tool that retrieves structured page content, more context is needed to use it effectively without trial and error.

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 schema description coverage is 100%, meaning all parameters are documented in the input schema. The description adds no additional parameter semantics beyond implying that 'page_id' identifies the target page and that content includes 'elements and their properties.' This meets the baseline for high schema coverage but doesn't enhance understanding of parameter usage.

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 tool's purpose: 'Get the content structure and data for a specific page including all elements and their properties.' It specifies the verb ('Get'), resource ('page content'), and scope ('structure and data for a specific page'). However, it doesn't explicitly differentiate from sibling tools like 'pages_get_metadata' or 'components_get_content', which reduces clarity in a crowded toolset.

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 doesn't mention sibling tools like 'pages_get_metadata' (for metadata only) or 'components_get_content' (for component content), nor does it specify prerequisites or exclusions. The agent must infer usage from the tool name and description alone.

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