Crawlora MCP

spotify_search

Read-only

Returns normalized Spotify Web Player catalog search results across tracks, artists, albums, playlists, shows, episodes, audiobooks, and top results. The endpoint fetches anonymous Spotify credentials at request time; caller-supplied Spotify bearer or client tokens are not required. limit: Result limit per section, clamped to 1-50, default 10. numberOfTopResults: Top result limit, clamped to 1-50, default 5. Use spotify_tracks_search to search Spotify tracks.

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_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/5.0

Behavior4/5

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

With readOnlyHint and openWorldHint already declared, the description adds genuinely useful non-structured context: credentials are fetched anonymously at request time and caller-supplied bearer/client tokens are not needed. It also notes results are 'normalized'. It stops short of describing pagination or rate-limit behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and auth behavior are front-loaded, but two sentences are spent repeating limit and numberOfTopResults details already present in the schema, which dilutes conciseness. Not egregious, but the redundant parameter restatement does not earn its place.

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 multiplexed 11-parameter search tool with an output schema and annotations, the description covers scope, auth behavior, and an alternative tool, leaving only pagination/rate-limit nuances unstated. Reasonably complete given the structured fields carry parameter and return details.

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 all 11 parameters. The description merely restates the limit and numberOfTopResults clamping/defaults verbatim, adding no meaning beyond the schema; 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?

States a specific verb ('Returns') and resource (Spotify Web Player catalog search results) and enumerates the covered content types (tracks, artists, albums, playlists, shows, episodes, audiobooks, top results), then explicitly names the sibling it is not: spotify_tracks_search. An agent can distinguish it from the per-type search siblings.

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

Usage Guidelines4/5

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

Provides a clear routing rule ('Use spotify_tracks_search to search Spotify tracks'), steering track-only queries away. However, it does not address the other obvious siblings (spotify_artists_search, spotify_albums_search, spotify_playlists_search, spotify_episodes_search), so the guidance is partial rather than exhaustive.

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.