mcp-spotify

get_audiobook_chapters

Retrieve chapters from a Spotify audiobook using its ID or URI, with options to limit results, set a market, or offset the starting chapter.

Instructions

Get Spotify catalog information about an audiobook's chapters

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_chapters"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	The Spotify ID or URI for the audiobook
`limit`	No	Maximum number of chapters to return (1-50)
`market`	No	Optional. An ISO 3166-1 alpha-2 country code
`offset`	No	The index of the first chapter to return

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.4Sep 11, 2026

TDQS

B3.1/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 for behavioral disclosure. It mentions 'catalog information' which implies read-only access, but doesn't specify authentication requirements, rate limits, pagination behavior (beyond what parameters suggest), error conditions, or response format. For a tool with 4 parameters and no output schema, this leaves significant behavioral gaps.

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 directly states the tool's purpose without unnecessary words. It's front-loaded with the core functionality and contains zero redundant information. Every word earns its place.

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

Completeness3/5

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

Given the tool's moderate complexity (4 parameters, no output schema, no annotations), the description is minimally adequate but incomplete. It covers the basic purpose but lacks behavioral context, usage guidelines, and output information. The 100% schema coverage helps, but without annotations or output schema, the description should do more to compensate.

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%, so the schema fully documents all 4 parameters. The description doesn't add any parameter-specific context beyond what's in the schema (e.g., it doesn't explain how 'market' affects results or provide examples of valid IDs). With complete schema coverage, the baseline score of 3 is appropriate.

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 about an audiobook's chapters'), making the purpose immediately understandable. It distinguishes from siblings like 'get_audiobook' by specifying chapters rather than general audiobook info, though it doesn't explicitly contrast with other chapter-related tools (none exist in the sibling list).

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 prerequisites (e.g., needing an audiobook ID), compare to similar tools like 'get_audiobook', or indicate scenarios where this is preferred over other catalog queries. Usage is implied but not explicitly stated.

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