Crawlora MCP

spotify_playlists_search

Read-only

Returns normalized Spotify Web Player playlist search results for a search term. 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_search to search Spotify catalog.

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_playlists_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?

Beyond the readOnlyHint/openWorldHint annotations, the description adds a genuinely useful behavioral fact: the endpoint fetches anonymous Spotify credentials at request time, so no caller-supplied bearer/client token is needed. It also flags the output as 'normalized', which matters for consumers. It omits pagination/rate-limit behavior, keeping it out of the top band.

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 auth sentence and the spotify_search pointer are well front-loaded and earn their place, but duplicating the limit/numberOfTopResults descriptions verbatim is pure redundancy against a 100%-covered schema. The paragraph drifts from purpose to auth to parameter text to alternative without tight ordering.

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?

An output schema exists, so return-value detail is unnecessary, and the description covers purpose, auth needs, and the main alternative. With 11 parameters of which 8 are undocumented in prose, the definition is complete enough for correct invocation though not rich.

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 repeats the limit and numberOfTopResults parameter text verbatim, adding no meaning beyond the schema, and says nothing about offset or the boolean include* flags. Baseline 3 is appropriate.

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+resource: 'Returns normalized Spotify Web Player playlist search results for a search term.' Among the many spotify_*_search siblings (albums, artists, tracks, shows, episodes), it pins down playlists exactly, and it explicitly names spotify_search as the general alternative.

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?

It gives a clear use case (playlist search) and points to spotify_search for general catalog search. It does not, however, explain why an agent would pick this over the other type-specific search tools (spotify_tracks_search, spotify_albums_search), so the routing guidance is clear but incomplete.

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.