Crawlora MCP

spotify_audiobooks_search

Read-only

Search Spotify's public Web Player catalog and return normalized audiobook search results for searchTerm; per-section and top-result counts are capped at 50. The endpoint fetches anonymous Spotify credentials at request time, so caller-supplied bearer or client tokens are not required. Use spotify_search for broad catalog queries or spotify_audiobook for one result's details.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "spotify_audiobooks_search"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Result limit per section, clamped to 1-50, default 10.
`offset`	No	Search offset, default 0.
`isPrefix`	No	Treat the search term as a prefix when set.
`searchTerm`	No	Spotify catalog search term (required).
`includeAuthors`	No	Include author results when true.
`includeAudiobooks`	No	Include audiobook results when true.
`includePreReleases`	No	Include pre-release results when true.
`numberOfTopResults`	No	Top result limit, clamped to 1-50, default 5.
`includeAlbumPreReleases`	No	Include album pre-release results when true.
`includeArtistHasConcertsField`	No	Request Spotify artist concert-availability fields when true.
`includeEpisodeContentRatingsV2`	No	Include Spotify episode content ratings v2 when true.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 7, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds genuinely new context: anonymous credentials are fetched at request time so no caller-supplied bearer/client tokens are needed, plus a 50-item cap on per-section and top-result counts. That materially affects invocation, though it doesn't discuss pagination behavior or result stability.

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?

Three tight sentences: what it does, the credential/limit constraint, then the alternative routing. Zero filler and the most important scoping information is front-loaded.

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 an output schema present, return values needn't be explained, and the description covers auth, caps, and sibling routing. It is nearly complete for an 11-param search tool; only pagination/interaction between limit and offset is left unstated.

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 every parameter (limit, offset, isPrefix, includeAuthors, etc.) is already documented. The description only restates the 50-item clamp that the schema already specifies per parameter, adding no new parameter-level meaning. Baseline 3 applies.

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?

The description gives a specific verb+resource ('Search Spotify's public Web Player catalog and return normalized audiobook search results') and explicitly distinguishes itself from two siblings by name. An agent can tell this apart from spotify_search and spotify_audiobook without opening any schema.

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

Usage Guidelines5/5

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

It names the alternatives and the conditions that select them: 'Use spotify_search for broad catalog queries or spotify_audiobook for one result's details.' This is an explicit routing rule, not inferred usage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.