docmost-mcp-oss

Overview Schema Source Related Servers Discussions Admin

List Child Pages

list_child_pages

Fetch direct child pages of a specific space or page. Retrieve only one hierarchy level, skipping deeper nesting. For a full tree, use get_workspace_overview.

Instructions

Lists only the direct children of a space or a page.

This is one level, not the whole tree. To enumerate everything in the workspace, use get_workspace_overview instead.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum number of results.
`page_id`	No	UUID or slugId of the parent page whose children you want (the `space_id` is resolved automatically).
`space_id`	No	UUID of the space whose root pages you want.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.6.0Sep 23, 2026

TDQS

A4/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 full burden. It discloses the depth limitation (direct children) and the alternative to avoid misuse, but does not mention return format, pagination, or potential errors. For a query tool, this is adequate but not rich.

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 remarkably concise—two sentences plus a note. It front-loads the most critical constraint (direct children only) and immediately follows with the alternative. No wasted words; every sentence earns its place.

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

Completeness4/5

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

The tool is simple, has an output schema, and schema covers all parameters. The description provides clear usage boundaries and routing to a sibling, which is sufficient for an agent to call correctly. Minor gaps like specifying that page_id and space_id are mutually exclusive are not critical due to schema hints.

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 the schema documents all three parameters. The description adds context on how page_id and space_id relate (one is resolved automatically), which goes slightly beyond schema, but it doesn't fully compensate for any ambiguity, e.g., what happens if both are provided.

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 states a specific verb ('Lists') and resource ('direct children of a space or a page'), and explicitly clarifies scope ('one level, not the whole tree'). It names the sibling alternative for broader enumeration, which distinguishes it from related tools like get_workspace_overview.

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?

It clearly states what the tool does (direct children only) and points to the alternative for full tree enumeration, but does not explicitly state when not to use it beyond that. The context of 'one level' implicitly guides correct usage.

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