mcp-spotify

get_audiobook

Retrieve Spotify catalog details for an audiobook using its ID or URI, with an optional market country code.

Instructions

Get Spotify catalog information for an audiobook

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "get_audiobook"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	The Spotify ID or URI for the audiobook
`market`	No	Optional. An ISO 3166-1 alpha-2 country code

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.4Sep 11, 2026

TDQS

C2.9/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action without detailing permissions, rate limits, response format, or error handling. This is inadequate for a tool that likely involves API calls and data retrieval.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with no wasted words. It's front-loaded with the core purpose, making it easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'catalog information' includes, how results are structured, or any behavioral aspects like authentication needs, leaving significant gaps for the agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, so the baseline is 3. The description doesn't add any parameter-specific information beyond what's in the schema, such as examples or constraints, but it doesn't need to compensate for gaps.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Get') and resource ('Spotify catalog information for an audiobook'), making the purpose evident. However, it doesn't explicitly differentiate from sibling tools like 'get_multiple_audiobooks' or 'get_audiobook_chapters', which would be needed for a score of 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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 versus alternatives like 'get_multiple_audiobooks' or 'get_audiobook_chapters'. The description lacks context about use cases or prerequisites, offering minimal direction for the agent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.