Retrieve a Goodreads Listopia ranked book list by ID with page-based pagination to browse ranked titles and gather list data.
Get a Goodreads Listopia list. Returns a Goodreads Listopia list (ranked book list) by id, paginated.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Goodreads list id | |
| page | No | 1-based page number, default 1 |
Changes observed during successful MCP inspections.
v1.5.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. It does disclose that output is a ranked list and that results are paginated, which is meaningful behavioral context, but says nothing about auth/permissions, rate limits, or error behavior for an invalid id.
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 short sentences, front-loaded with the core purpose. The second sentence partially restates the first ('Returns a Goodreads Listopia list...'), a minor redundancy, but the pagination note 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?
For a simple two-parameter, read-only lookup with 100% schema coverage and no output schema, the description adequately covers what is returned (a ranked book list) and that it is paginated. Missing only auth/limit context, which matters less for a public read.
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 the schema already documents both id and page. The description restates 'by id' and 'paginated' but adds no syntax, range, or format detail beyond the schema, 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?
States a clear verb and resource ('Get a Goodreads Listopia list') and clarifies it is a ranked book list retrieved by id. It distinguishes itself implicitly from the plural sibling goodreads_lists by the 'by id' framing, but does not explicitly name that sibling to remove ambiguity.
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 offers no when-to-use guidance, no conditions, and does not name any alternative (e.g. goodreads_lists for browsing or goodreads_search for discovery). The agent must infer that this is the id-lookup tool rather than the browse tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.