Retrieve a page's revision history to review past changes, track edits, and audit updates in a Docmost wiki. Use page_id with optional limit and cursor for pagination.
List revision history for a page.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Page size, 1-100 | |
| cursor | No | Pagination cursor from meta.nextCursor | |
| page_id | Yes | Page UUID or slugId |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds no additional behavioral context, such as ordering of revisions, whether deleted revisions are included, or what fields each history item contains.
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 filler. It loses a point only because it is so terse that it carries no information beyond the tool's obvious purpose, though the brevity itself is appropriate.
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 read-only list operation with well-documented parameters and safety annotations, the description is minimally adequate. However, there is no output schema and no mention of return shape, ordering, or pagination behavior beyond the cursor parameter, so an agent navigating history data would need more context.
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 the schema already documents all three parameters. The description does not add parameter-level meaning beyond 'page' scope, but it doesn't need to; 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 states a clear verb ('List') and resource ('revision history for a page'), and the plural 'history' distinguishes it from the singular get_history_version sibling. However, it doesn't explicitly call out that distinction or mention what a history entry contains, 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?
No when-to-use guidance is provided. The description does not mention get_history_version or any other alternative, nor does it give conditions for when list vs. get history is appropriate, leaving the agent to infer from sibling names.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.