Webflow MCP Server

pages_list

Get a list of all pages in a Webflow site, including page IDs, titles, and slugs. Paginate with limit and offset, and filter by locale.

Instructions

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

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": {
      "site_id": "<site_id>"
    },
    "name": "pages_list"
  }
}

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.
`site_id`	Yes	The site’s unique ID, used to list its pages.
`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.7/5.0

Behavior3/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. It states a read operation ('List') and return fields, but does not disclose pagination behavior (limit/offset), localization, or any side effects. The phrase 'all pages' may be inaccurate if a default limit applies.

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?

A single sentence, front-loaded with the action, and no extraneous words.

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?

The description covers the basic purpose and return fields, but for a list tool with pagination and locale parameters, it leaves important behavior (paging, localization) unstated. No output schema exists, so more detail would be helpful.

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%, so each parameter is already described. The description adds no parameter-specific meaning beyond the schema; it only mentions return fields.

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 uses a specific verb ('List') and resource ('pages within a site'), and specifies the return content (metadata including IDs, titles, and slugs). It clearly distinguishes from sibling tools like pages_get_metadata (single page) and collections_list (different resource).

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 enumerating pages in a site but does not explicitly state when to prefer this over pages_get_metadata or how pagination works. No alternatives are mentioned.

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