docraptor_list_documentsList metadata for documents created on this account, most recent first (paginated). Note: DocRaptor does not retain the rendered files themselves — this returns metadata such as name, type, test flag, and creation time. DocRaptor API: GET /docs.json.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Pagination page number. Default 1. | |
| per_page | No | Documents per page (max 100). Default 100. |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations indicate readOnlyHint=true, and the description reinforces that it lists metadata without destructive actions. It adds context that files are not retained, which goes beyond annotations, but doesn't disclose rate limits or authentication needs.
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?
Two sentences, no redundancy. Key information is front-loaded: purpose, order, pagination, and a critical note about what is returned. Every sentence is valuable.
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?
No output schema exists, but the description compensates by listing the type of metadata returned (name, type, test flag, creation time). It also mentions pagination and ordering. While not exhaustive on response structure, it is adequate for a simple list tool.
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% with clear descriptions for page and per_page. The description adds context about pagination and ordering (most recent first), which complements the schema and adds value beyond the parameter descriptions.
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 it lists metadata for documents on the account, most recent first, paginated. It distinguishes from sibling tools by specifying it returns metadata, not rendered files, and contrasts with create, status, and IP list tools.
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?
The description provides context about what is returned (metadata, not files) and pagination, helping an agent decide when to use it. However, it doesn't explicitly state when to use this over get_document_status or alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.