list_recent_pagesRetrieve recently updated pages from a Docmost workspace, optionally filtered by space ID. Specify a limit to control how many results are returned.
Lists recently updated pages.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of results. | |
| space_id | No | UUID of the space (optional; without it, from the whole workspace). |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.6.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations are absent, so the description carries the full burden. It states the core behavior (listing recently updated pages) but adds no detail on ordering, pagination, what 'recently' means, or whether it returns full pages or summaries. It fails to disclose any behavioral traits beyond the literal action.
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, clear sentence with no redundancy. It is appropriately front-loaded and efficient, conveying the essential purpose without fluff.
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?
Given the presence of a complete schema and an output schema, the description is minimally adequate. However, it omits important contextual details such as sort order (by update time descending), handling of the optional space_id (workspace-wide if omitted), and any implicit limits. These are not covered by annotations, leaving some ambiguity for an agent deciding how to call it.
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 coverage is 100%, so both parameters (limit and space_id) are already documented. The description adds no additional meaning about parameters—it does not explain how limit or space_id affect results beyond what the schema states. Baseline 3 applies.
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?
The description clearly states a specific action ('Lists') and resource ('pages'), with a qualifier ('recently updated'). It distinguishes from siblings like get_page (single page) and search_pages (search), but does not explicitly name alternatives or contrast them, so it's not 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?
No guidance is provided on when to use this tool versus siblings. It does not mention alternatives, exclusions, or contextual cues for selection. The description is purely functional without any usage direction.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.