Fetch chapters from a Spotify audiobook by show ID, URI, or show URL. Use limit and offset to page through results in JSON.
Retrieve Spotify audiobook chapters. Returns audiobook chapters from Spotify Web Player private Pathfinder responses.
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | Spotify show ID | |
| uri | No | Spotify audiobook/show URI or open.spotify.com show URL | |
| limit | No | Chapter limit, clamped to 1-50 | |
| offset | No | Chapter offset |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description must fully disclose behavior. It indicates the tool returns data from 'private Pathfinder responses' but fails to state whether it is read-only, requires authentication, or has rate limits. No side effects or return structure are mentioned, leaving significant ambiguity.
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?
The description is extremely concise with two sentences, front-loading the purpose. However, it is so brief that it sacrifices useful context. While no words are wasted, it could be slightly expanded for clarity without becoming verbose.
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?
With 4 parameters, no output schema, and no annotations, the description omits critical details such as response format, pagination behavior, and error handling. The sibling list includes many Spotify tools but no cross-referencing is provided. The description is insufficient for an agent to use this tool reliably without external knowledge.
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 all parameters described. The description adds no additional meaning beyond the schema; it does not explain parameter relationships (e.g., uri vs id exclusivity, offset/limit for pagination). Baseline 3 is appropriate.
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 the tool retrieves Spotify audiobook chapters, using a specific verb and resource. It distinguishes from siblings like spotify_audiobook (full audiobook) and spotify_chapter (single chapter) by specifying chapters. The mention of 'private Pathfinder responses' adds technical context but doesn't obscure purpose.
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 guidance is provided on when to use this tool vs alternatives such as spotify_audiobook or spotify_chapter. There is no mention of prerequisites, conditions, or exclusions. The agent must infer usage from the name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.