Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

spotify_chapter

Fetch Spotify audiobook chapter details by URI or ID, including name, duration, release date, playability, preview audio, cover images, and parent show.

Instructions

Retrieve Spotify audiobook chapter details. Returns a Spotify audiobook chapter by uri or id; chapters are often addressed with spotify:episode: identifiers. Fields include name, description, duration, release date, explicit and paywall flags, playability reasons, preview audio URL, cover images and the parent show. An invalid identifier returns 400.

Input Schema

NameRequiredDescriptionDefault
idNoSpotify chapter/episode ID
uriNoSpotify chapter or episode URI/URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/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 burden and does reasonably well: it enumerates the returned fields (name, duration, explicit/paywall flags, playability reasons, preview URL, cover images, parent show) and discloses error behavior ('An invalid identifier returns 400') plus the quirk that chapters use episode-style identifiers. It omits auth/market-availability requirements, so it stops short of a 5.

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?

Three front-loaded sentences: purpose, identifier mechanics, and return/error details. Dense but every sentence carries information; it could be tightened slightly but no sentence is filler.

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 two-param read tool with no annotations and no output schema, the description usefully compensates by listing the returned fields and the 400 error case. It lacks auth/scope expectations and any sibling-routing guidance, which keeps it from being fully complete.

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 coverage is 100% and both params are documented in the schema, so baseline 3 applies. The description adds a useful note that `spotify:episode:` identifiers are typical, but does not clarify whether passing both `id` and `uri` is allowed or how they take precedence.

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?

States a specific verb (Retrieve) and resource (Spotify audiobook chapter), and clarifies that chapters are often addressed via `spotify:episode:` identifiers, which helps separate it from a generic episode tool. It does not, however, explicitly contrast itself with close siblings like spotify_podcasts_episode or spotify_audiobook_chapters.

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

Usage Guidelines3/5

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

Usage is only implied by the mention of required identifiers (uri/id). There is no explicit when-to-use guidance, no statement of when NOT to use it, and no pointer to the sibling that handles audiobook chapter lists or episode search.

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