Retrieve all Zola wedding-website pages, including IDs, page types, display order, visibility, and theme details. Use this to review or manage your site structure.
List all wedding-website pages with their IDs, types, display order, visibility, and theme info
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.4.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already carry readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the returned-field inventory, which helps the agent know what it gets back, but discloses nothing about pagination, ordering guarantees, or auth needs.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One front-loaded sentence, no filler. Every clause (resource, ID, type, display order, visibility, theme) carries information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema exists, so describing the returned fields in the description is a real contribution. The tool is a trivial zero-param list, so it is nearly complete, though return-shape details (e.g., ordering, count) are absent.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Zero parameters, so the baseline is 4. The description doesn't need to explain parameters, and it helpfully documents what the call returns instead.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (List) and resource (wedding-website pages) and enumerates the exact fields returned (IDs, types, display order, visibility, theme info). An agent can distinguish this from sibling mutation tools like update_page or reorder_pages without opening the schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit when-to-use or alternatives stated, but the read-only list semantics combined with siblings set_page_hidden/reorder_pages/update_page imply this is the discovery step before those mutations. Usage is inferable but not spelled out.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.