Webflow MCP Server

pages_get_content

Retrieve page content structure and data, including all elements and their properties. Use page_id to specify the target page.

Instructions

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

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "page_id": "<page_id>"
    },
    "name": "pages_get_content"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Maximum number of records to be returned (max limit: 100)
`offset`	No	Offset used for pagination if the results have more than limit records.
`page_id`	Yes	Unique identifier for the page.
`localeId`	No	Unique identifier for a specific locale. Applicable when using localization.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.7.0Aug 9, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations provided, the description carries the transparency burden. It indicates a read operation via 'Get' and describes the return as content structure and data, but it does not mention pagination, localization, or any limitations. The read-only nature is implied but not explicit, and response format details are absent.

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 concise sentence of 17 words, front-loaded with the verb and resource. Every word contributes to the core purpose, with no fluff or redundancy, making it appropriately sized for a simple get operation.

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 absence of an output schema and annotations, the description should provide more context about response shape and pagination. It mentions 'all elements and their properties' but does not explain how limit/offset affect results or how localeId modifies behavior. This is a significant gap for a data-fetching tool.

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 coverage is 100%, with descriptions for all four parameters. The description adds only a slight context that it applies to a 'specific page', which maps to page_id, but it does not enrich understanding of limit, offset, or localeId beyond what the schema already provides. Baseline of 3 is appropriate.

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 a specific verb ('Get') and resource ('content structure and data for a specific page'). It distinguishes from siblings like pages_get_metadata or pages_list by focusing on page content and elements, making the purpose unambiguous.

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 retrieving content of a specific page, but it does not explicitly discuss when to use this tool versus alternatives like components_get_content or pages_get_metadata. It provides clear context ('specific page') but no exclusions or alternative guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.