mcp-spotify

get_multiple_audiobooks

Retrieve Spotify catalog details for multiple audiobooks by ID or URI, with optional market code filtering.

Instructions

Get Spotify catalog information for multiple audiobooks

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": {
      "ids": "<ids>"
    },
    "name": "get_multiple_audiobooks"
  }
}

Input Schema

Name	Required	Description	Default
`ids`	Yes	Array of Spotify audiobook IDs or URIs (max 50)
`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 full burden but offers minimal behavioral insight. It states it retrieves 'catalog information' but doesn't detail what that includes (e.g., metadata, availability), response format, error handling, or constraints like rate limits. The description lacks critical context for a read operation in a rate-limited API environment.

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 that front-loads the core purpose without unnecessary words. It directly addresses what the tool does, making it easy to parse and understand quickly. Every word earns its place.

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 no annotations and no output schema, the description is incomplete for effective tool use. It doesn't explain what 'catalog information' entails, response structure, error cases, or authentication needs. For a batch retrieval tool in a complex API like Spotify, more context is needed to complement the well-documented input schema.

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?

Schema description coverage is 100%, with both parameters ('ids' and 'market') well-documented in the schema itself. The description adds no additional parameter semantics beyond implying batch retrieval via 'multiple audiobooks', which aligns with the 'ids' array parameter. This meets the baseline for high schema coverage.

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 verb ('Get') and resource ('Spotify catalog information for multiple audiobooks'), making the purpose immediately understandable. It distinguishes from sibling 'get_audiobook' by specifying 'multiple' audiobooks, though it doesn't explicitly contrast with other catalog lookup tools like 'get_multiple_albums' or 'get_multiple_artists' beyond the resource type.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention when to prefer this over 'get_audiobook' (for single vs. batch retrieval) or other catalog tools, nor does it specify prerequisites like authentication or rate limits. Usage context is implied only by the tool name and description.

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