Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_audiobook_chapters

Retrieve paginated chapter lists for any Spotify audiobook by ID, with optional limit and offset controls.

Instructions

List the chapters of an audiobook with pagination. Audiobooks are only available in the US, UK, Canada, Ireland, New Zealand and Australia markets.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesSpotify audiobook ID
limitNoResults per page, 1–50. Default: 20
marketNoISO 3166-1 alpha-2 country code. If given, only content available in that market is returned. Audiobooks are only available in the US, UK, Canada, Ireland, New Zealand and Australia markets.
offsetNoIndex of the first chapter to return. Default: 0
max_resultsNoMax items to return (default: SPOTIFY_MCP_MAX_ITEMS env or 50)
response_formatNo'concise' = human prose, 'detailed' = more fields in prose, 'json' = raw API objectconcise

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.26.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / market / pattern
      Added value: +"^[A-Za-z]{2}$"
    • addedInput schema / properties / max_results
      Added value: +{
+  "description": "Max items to return (default: SPOTIFY_MCP_MAX_ITEMS env or 50)",
+  "exclusiveMinimum": 0,
+  "maximum": 2000,
+  "type": "integer"
+}
    • addedInput schema / properties / offset / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / response_format
      Added value: +{
+  "default": "concise",
+  "description": "'concise' = human prose, 'detailed' = more fields in prose, 'json' = raw API object",
+  "enum": [
+    "concise",
+    "detailed",
+    "json"
+  ],
+  "type": "string"
+}
  2. First observedv1.0.1

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It adds a useful market restriction ('Audiobooks are only available in...'), but otherwise mostly restates pagination, which is already visible in the limit/offset schema. It does not disclose return shape, response_format behavior, or error conditions, though these are less critical for a read-only list operation.

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?

Two tight sentences with no filler. The action and resource are front-loaded, and the market note is a concise, useful addition.

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?

The schema fully documents the parameters and the core call is clear, but there is no output schema and no guidance to help an agent choose among the many audiobook-related sibling tools. The missing return-format and when-to-use notes leave it slightly under-specified.

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 all six parameters are already documented in the schema. The description adds no meaningful parameter-level detail beyond the market restriction, which is also repeated in the market parameter's schema description. Baseline 3 applies.

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 uses a specific verb ('List') and resource ('chapters of an audiobook'), and mentions pagination. However, it does not explicitly distinguish itself from sibling tools like get_chapter, get_several_chapters, or audiobook_chapter_map, so an agent must infer the exact scope from the name and schema.

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 given on when to use this tool versus get_chapter, get_several_chapters, or list_all_chapters. The market-availability note is a constraint, not usage context, and no alternatives or exclusions are mentioned.

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

Deploy Server

Other Tools