Retrieve recently modified pages in a Collective, sorted by last edit time. Specify a limit to control the number of results returned.
List recently-modified pages for a Collective, ordered by last edit time.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum pages to return (default 25, max 100). | |
| collectiveId | Yes | Collective id from list_collectives. |
Changes observed during successful MCP inspections.
v0.2.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the ordering-by-last-edit-time behavior, which is useful, but it does not mention pagination defaults (limit) or any edge cases. Given the annotation coverage, a 3 is appropriate – it adds some behavioral context without being exhaustive.
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, well-structured sentence that front-loads the action and scope. No filler or redundancy – every word earns its place.
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?
The tool is a simple read-only list operation with only two parameters, both fully documented in the schema. The description explains the purpose and ordering. Although there is no output schema and the return format is unspecified, that is typical for list operations and not a critical gap given the tool's simplicity.
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% – both 'limit' and 'collectiveId' have clear descriptions. The tool description does not add anything about parameter semantics beyond what the schema already provides, so the 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'), a specific resource ('recently-modified pages for a Collective'), and an ordering constraint ('ordered by last edit time'). This distinguishes it from the sibling 'list_pages' by scope (recent vs all) without needing to open 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?
There is no guidance on when to use this tool versus alternatives like 'list_pages' or 'search'. The context implies it is for recent pages, but no explicit when/when-not or alternative routing is provided, leaving the agent to infer the selection criteria.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.