Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

spotify_audiobook_chapters

Retrieve chapters for any Spotify audiobook using its URI, open.spotify.com URL, or ID, with offset and limit pagination; returns names, durations, dates, URLs, and images.

Instructions

Retrieve Spotify audiobook chapters. Returns the chapters of a Spotify audiobook by URI, open.spotify.com URL or id, with offset and limit (1-50, default 50). Each chapter has its name, description, duration in milliseconds, release date, explicit and playable flags, Spotify URI, external URL and images; total gives the chapter count.

Input Schema

NameRequiredDescriptionDefault
idNoSpotify show ID
uriNoSpotify audiobook/show URI or open.spotify.com show URL
limitNoChapter limit, clamped to 1-50
offsetNoChapter offset

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are present, so the description carries the full burden. It adds useful behavioral context: pagination via offset/limit, an enforced 1-50 clamp with a default of 50, and the fields returned per chapter plus a total count. It omits auth requirements, error behavior, and whether id/uri are effectively required in practice.

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?

Two sentences, purpose front-loaded, then the return shape. The chapter-field enumeration is long but earns its place by substituting for a missing output schema. No wasted preamble.

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?

With no output schema, the description appropriately details the returned fields and total count. With no annotations, it should ideally note read-only/auth behavior, but for a simple paginated read tool the purpose, input formats, and return shape are otherwise complete.

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 the schema already documents all four parameters (baseline 3). The description goes beyond it by adding the default limit value (50) and clarifying that the identifier accepts a URI, an open.spotify.com URL, or an id, which the schema's shorthand does not spell out.

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?

States a specific verb (Retrieve) plus the exact resource (Spotify audiobook chapters), and the scope of the listing. An agent can distinguish it from siblings like spotify_chapter or spotify_audiobook without opening the schema.

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 implied: use this to enumerate the chapters belonging to one audiobook. However, there is no explicit when-to-use versus alternatives (e.g. spotify_chapter for a single chapter, spotify_audiobook for metadata), and no stated prerequisites or exclusions.

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