Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_audiobook

Fetch full audiobook details by Spotify ID. Specify an optional market to check availability in supported countries, and choose concise, detailed, or raw JSON output.

Instructions

Get full details for an audiobook by ID. Audiobooks are only available in the US, UK, Canada, Ireland, New Zealand and Australia markets.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesSpotify audiobook 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

B3.1/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 behavioral burden. It adds only the market availability caveat, which largely duplicates the market parameter's schema text, and does not describe default market behavior, what 'full details' includes, permission needs, or response characteristics.

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 short sentences front-load the core lookup action and then add the market scope caveat. There is no filler or redundant restatement of the tool name, and every sentence 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?

For a simple single-item getter with complete schema coverage, the essential facts are present: lookup by ID, market restriction, and output format is defined by response_format. However, with no annotations, no output schema, and many related audiobook siblings, the definition would be stronger with guidance on when to use it and what 'full details' actually returns.

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 already fully documents id, market, and response_format. The description adds no new parameter-level meaning beyond the schema, meeting the baseline for high 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 states a clear action and resource: 'Get full details for an audiobook by ID.' It indicates a singular, ID-based lookup and is distinguishable from plural/search audiobook tools, though it does not explicitly name any sibling alternative.

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 gives no guidance on when to use this tool versus alternatives such as get_several_audiobooks, search_audiobooks, or get_audiobook_chapters. It implies the agent should already have an ID, but does not state when this tool is preferred or when another should be used.

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