Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

spotify_audiobooks_search

Search Spotify audiobooks by keyword and get JSON results with optional limits, authors, pre-releases, and ratings. No Spotify bearer or client tokens are required.

Instructions

Search Spotify audiobooks. Returns Spotify audiobook search results for a search term. Caller-supplied Spotify bearer or client tokens are not required.

Input Schema

NameRequiredDescriptionDefault
qYesSearch term
limitNoAudiobook result limit, clamped to 1-50
offsetNoSearch offset
include_authorsNoInclude authors
include_audiobooksNoInclude audiobook results
include_pre_releasesNoInclude pre-release results
number_of_top_resultsNoTop result limit, clamped to 1-50
include_album_pre_releasesNoInclude album pre-release results
include_episode_content_ratings_v2NoInclude Spotify episode content ratings v2

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that caller-supplied Spotify bearer or client tokens are not required, but it does not explain pagination behavior despite limit/offset parameters, nor does it describe rate limits or result structure beyond 'search results.'

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?

The description is short and front-loaded with the tool purpose. The second sentence partly restates the first but also adds the useful auth note, leaving little wasted space overall.

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 9-parameter search tool with no annotations and no output schema, the description is quite thin. The rich parameter schema compensates for missing parameter details, but the description says little about optional filters, pagination, or the shape of the returned search results.

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 documents q, limit, offset, and the inclusion flags. The description adds only the phrase 'search term,' which repeats the q schema description, so it does not add meaning beyond the structured parameter documentation.

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 specific verb and resource: 'Search Spotify audiobooks' and 'Returns Spotify audiobook search results for a search term.' It clearly scopes the tool to audiobooks, but it does not name or differentiate from sibling search tools such as spotify_search or spotify_audiobook.

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 by the search term requirement, but the description gives no explicit guidance on when to use this versus general Spotify search or audiobook-detail tools. It also provides no when-not conditions or alternatives.

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