WebCake Landing MCP

find_pages

Read-only

Searches the account's pages by name, domain and/or page id. Filters are AND-combined; name and domain are case-insensitive substrings, and domain matches custom_domain or default_domain.

Instructions

Searches the account's pages by name, domain and/or page id. Filters are AND-combined; name and domain are case-insensitive substrings, and domain matches custom_domain or default_domain. Each result includes id, name, organization_id, custom_domain, default_domain and updated_at. With no filters it returns the most recently updated pages. Requires Webcake credentials.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_pages"
  }
}

Input Schema

Name	Required	Description
`name`	No	Case-insensitive substring of the page name to match.
`limit`	No	Max results (default 50, capped at 100).
`domain`	No	Case-insensitive substring of the page's domain (matches custom_domain OR default_domain).
`page_id`	No	Exact page id — narrows to that single page (useful to confirm it exists/owned).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.5.0Jul 30, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint, so the description carries the extra load and does so well: it discloses AND-combination semantics, case-insensitive substring matching, the custom_domain-or-default_domain matching rule, the no-filter default ordering, the credential requirement, and the result field set. That is rich behavioral context beyond the annotations.

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?

Three dense sentences with no filler. The search scope is front-loaded, followed by matching semantics, default behavior, result fields, and prerequisites in a logical order.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, but the description compensates by listing the returned fields (id, name, organization_id, custom_domain, default_domain, updated_at). Combined with the auth requirement and matching semantics, an agent has everything needed to call and interpret this tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the per-parameter details already exist and baseline is 3. The description goes a step further by explaining the interaction between parameters (AND-combined) and clarifying that domain matches either custom_domain or default_domain — relationship semantics the schema cannot express on its own.

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?

States a specific verb and resource ('Searches the account's pages') and enumerates what can be searched on (name, domain, page id), which clearly separates it from get_page or list_elements. It stops short of explicitly naming a sibling such as list_pages or get_page, so the differentiation is inferable rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete call conditions: filters are AND-combined, and with no filters it returns the most recently updated pages. It also hints page_id is useful to confirm a page exists/is owned. No explicit exclusions or named alternatives are offered, but the context needed to pick this tool is present.

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