Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_chapter

Retrieve complete metadata for an audiobook chapter via its Spotify ID, including market availability and playback position when authorized.

Instructions

Get full details for a single audiobook chapter by ID. Resume position requires the user-read-playback-position scope. Audiobooks are only available in the US, UK, Canada, Ireland, New Zealand and Australia markets.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesSpotify chapter ID
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.
response_formatNo'concise' = human prose, 'detailed' = more fields in prose, 'json' = raw API objectconcise

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 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 / 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

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the full behavioral disclosure burden. It adds meaningful context about a required OAuth scope for resume position and restricts audiobook availability to specific markets. This goes beyond the basic 'get details' statement, though it does not describe response shape or error behavior.

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 sentences carry the core purpose plus the two most important caveats (scope and market restriction). There is no filler or redundancy.

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?

For a single-resource lookup with three parameters and no output schema, the description covers identity, scope prerequisites, and market constraints. It could be more complete by describing what fields constitute 'full details,' but it gives an agent enough to invoke correctly.

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 baseline is 3. The description itself adds no parameter detail beyond the schema; the 'by ID' phrase merely echoes id, and market/response_format semantics are already fully documented in the schema.

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 uses a specific verb and resource: 'Get full details for a single audiobook chapter by ID.' This clearly differentiates it from sibling tools like get_audiobook_chapters (list) and get_audiobook (audiobook-level details).

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

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description makes the usage context clear: call this when you need full details for one chapter identified by its ID. It does not explicitly name alternatives or exclusions, but the 'single ... by ID' phrasing provides sufficient routing context among siblings.

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