Spotify MCP Server

by llyfn

Overview Schema Source Related Servers Discussions Admin

Python

Remote

get_audiobook_chapters

Retrieve chapters of a Spotify audiobook by providing its ID. Specify limit, offset, and market for tailored results.

Instructions

Get chapters of a Spotify audiobook.

    Args:
        audiobook_id: The Spotify ID of the audiobook.
        limit: Maximum number of chapters to return (1-50, default 20).
        offset: Index of the first chapter to return (default 0).
        market: ISO 3166-1 alpha-2 country code.

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": {
      "audiobook_id": "<audiobook_id>"
    },
    "name": "get_audiobook_chapters"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`market`	No
`offset`	No
`audiobook_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.2.0Jun 9, 2026

addedInput schema / properties / market

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Market"
+}

First observedv0.1.1May 5, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. While 'Get' implies a read-only operation, the description does not explicitly state that it is non-destructive, nor does it disclose any additional behavioral traits like required authentication or rate limits.

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

Conciseness4/5

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

The description is concise and uses a clear Args section structure. However, it includes the 'Args:' prefix which is typical for docstrings but adds a minor overhead. The information is well front-loaded.

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

Completeness4/5

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

The tool has an output schema, so return values need no explanation. The description adequately covers the input parameters and basic behavior. However, it lacks context about the response structure or pagination in the output, which could be inferred from the output schema but isn't mentioned.

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

Parameters5/5

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

With 0% schema description coverage, the description is essential. It adds concrete meaning to all parameters: audiobook_id (the Spotify ID), limit (1-50, default 20), offset (default 0), and market (ISO 3166-1 alpha-2 country code). This goes far beyond the schema's type-only definitions.

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

Purpose5/5

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

The description starts with a clear verb-noun phrase 'Get chapters of a Spotify audiobook,' specifying the exact resource and action. This distinguishes it from sibling tools like get_audiobook (which retrieves the audiobook itself) and get_chapters (which retrieves specific chapters by ID).

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 such as get_chapters, which might be used to fetch specific chapters by ID. The context of pagination (limit, offset) is implied but not explicitly tied to usage scenarios.

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