Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

spotify_audiobook

Retrieve Spotify audiobook details by show URI or ID, returning authors, narrators, publisher, chapter count, and cover images.

Instructions

Retrieve Spotify audiobook details. Returns a Spotify audiobook by uri or id; Spotify identifies audiobooks with show URIs (spotify:show:...). The response has name, authors, narrators, publisher, description, totalChapters, explicit flag and cover images. Passing a podcast show instead of an audiobook returns an upstream error, and an invalid identifier returns 400.

Input Schema

NameRequiredDescriptionDefault
idNoSpotify show ID
uriNoSpotify audiobook/show URI or open.spotify.com show URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose concrete behavior: the audiobook/show URI convention and two distinct failure modes (upstream error for a podcast show, 400 for an invalid identifier). It omits auth requirements and read-only framing, but the edge-case disclosure is well above baseline.

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, front-loaded with purpose, then the identifier convention, return fields, and error behavior. Every clause earns its place with no 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?

No output schema exists, and the description compensates by enumerating the returned fields (name, authors, narrators, publisher, totalChapters, explicit, images). Combined with error semantics, it is nearly complete for a simple retrieval tool, missing only auth/rate-limit context.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds real semantic value by explaining that audiobooks are addressed with show URIs (spotify:show:...) and that both `id` and `uri` identify the same resource. This resolves the ambiguity that `id` is a show ID rather than a distinct audiobook ID.

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 details) and clarifies the ID model (audiobooks use show URIs). It partially differentiates from siblings by noting that passing a podcast show errors out, though it never names the relevant alternatives like spotify_podcasts_show or spotify_audiobooks_search.

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: an agent gathers that this is a lookup-by-identifier tool and that a podcast show input is invalid. There is no explicit when-to-use guidance, no prerequisites, and no routing to sibling tools for discovery or chapter listing.

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