Fetch Spotify audiobook metadata from show IDs, URIs, or open.spotify.com URLs to retrieve audiobook details via private Pathfinder responses.
Retrieve Spotify audiobook details. Returns Spotify Web Player audiobook metadata from private Pathfinder responses. Spotify exposes audiobooks through show URIs.
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | Spotify show ID | |
| uri | No | Spotify audiobook/show URI or open.spotify.com show URL |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description must carry full burden. It hints at private source and show URI association, but lacks details on side effects, authentication, rate limits, error handling, or response format. For a data retrieval tool, more behavioral context is needed.
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 sentences, each serving a purpose: stating action, source, and domain fact. No superfluous words, but could potentially combine sentences for tighter structure. Still, good conciseness.
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?
Given no output schema and many sibling tools, the description should clarify that this tool retrieves metadata for a specific audiobook by URI/ID, and that search or chapter tools are for other tasks. It does not provide enough context for an agent to reliably select it. Vague on output ('audiobook metadata').
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 parameter descriptions are already clear. The description adds the insight that audiobooks are exposed through show URIs, which ties parameters to the domain, but does not significantly enhance meaning beyond what's in the schema. 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?
Description clearly states 'Retrieve Spotify audiobook details' as a specific verb+resource. It mentions the source (private Pathfinder responses) and that audiobooks use show URIs. However, it does not explicitly differentiate from sibling tools like spotify_audiobook_chapters or spotify_audiobooks_search.
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 on when to use this tool versus alternatives. Does not mention search tools for finding audiobooks or chapter retrieval. Agent receives no context for decision-making.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.