Get an Audible series' ordered book list using its series ASIN, so you can retrieve every book in sequence.
Get an Audible series' ordered book list. Returns an Audible series and every book in it, in series order. A series has its own ASIN distinct from any book in it — find one via a book's series[].asin field from GET /audible/product/{asin}.
| Name | Required | Description | Default |
|---|---|---|---|
| asin | Yes | Audible series ASIN, from a product's series[].asin field |
Changes observed during successful MCP inspections.
v1.16.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations and no output schema, the description carries the full burden, and it delivers the key behavioral fact: the result is the series object plus all member books returned in reading/series order. It does not mention pagination, result caps, or that the ASIN must be a series ASIN (enforced by the sibling product tool chain), so it stops short of full disclosure.
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?
Three short sentences, front-loaded with the purpose, then the return shape, then the identifier provenance. Nothing is redundant or padded.
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 one-parameter read tool with no annotations or output schema, the description covers what it returns and how to source the input. Only minor gaps remain (ordering semantics beyond 'series order', result limits), which are not critical for correct invocation.
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% and already defines the single asin parameter, so the baseline is 3. The description adds value by tracing that identifier to its concrete source endpoint (GET /audible/product/{asin}), reducing the chance of passing a book ASIN instead of a series ASIN.
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 specific verb and resource ('Get an Audible series' ordered book list') and immediately clarifies the payload is the series plus every book in series order. This cleanly separates it from audible_product / audible_products, which operate on books rather than series.
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?
It tells the agent the prerequisite for invocation: a series has its own ASIN, obtainable from a book's series[].asin field via GET /audible/product/{asin}. That is a real usage instruction, but there is no explicit when-not or alternative routing (e.g. 'use audible_search if you only have a title').
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.