list_pagesRetrieve top-level Docmost wiki pages for a space, or fetch direct child pages by parent page ID.
Lists the top-level pages of a space, or the direct children of a page when parentPageId is given.
| Name | Required | Description | Default |
|---|---|---|---|
| spaceId | No | Space id from list_spaces; lists the root pages of that space. | |
| parentPageId | No | Lists the direct children of this page instead. |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses the parentPageId branching, but that behavior is already documented in the schema, and the description says nothing about read-only safety, ordering, or pagination limits for a list operation.
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?
A single, front-loaded sentence with no waste. It could be marginally tighter but is efficient and easy to scan.
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?
For a low-complexity list tool with full schema coverage, the description is adequate but omits pagination/ordering behavior and read-only confirmation, which matter for a listing endpoint with no annotations or output schema.
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?
Schema description coverage is 100%, so both parameters are already well documented. The description only restates the parentPageId behavior already present in the schema, adding no new semantic detail.
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 ('Lists') and resource ('pages') and clarifies the two modes of operation (top-level space pages vs. direct children). It does not explicitly distinguish itself from siblings like search_pages or get_page, so it falls just short of a 5.
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?
Implies usage via the parentPageId conditional, but gives no explicit guidance on when to prefer this over search_pages or get_page, nor any prerequisites. Usage must be inferred.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.