Crawlora MCP

spotify_podcasts_search

Read-only

Search Spotify's public Web Player for podcast shows, episodes, and top-result items using searchTerm; anonymous credentials are fetched at request time, so caller tokens are not required. Use spotify_episodes_search for episodes, spotify_shows_search for shows, spotify_search for broad queries, or spotify_podcasts_show for one show.

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_podcasts_search"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Result limit per section, clamped to 1-50, default 30.
`offset`	No	Search offset, default 0.
`searchTerm`	No	Spotify podcast 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.
`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 5, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint. The description adds genuinely useful context beyond them: credentials are anonymous and fetched at request time, so callers need no tokens. It does not describe pagination behavior, but the output schema exists and covers return values.

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, front-loaded with purpose before the routing guidance, with no filler. Minor redundancy in saying it searches 'episodes' and then pointing to spotify_episodes_search for episodes, but the structure is efficient.

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 returns need not be explained, and annotations cover the safety profile; the description fills the auth gap and routes to siblings. For a nine-parameter search tool this is largely complete, with only the positive selection condition left implicit.

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 all nine parameters are already documented, and the description only references `searchTerm` and 'top-result' implicitly. Baseline 3 applies when the schema carries the parameter burden.

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 ('Search Spotify's public Web Player for podcast shows, episodes, and top-result items') and distinguishes itself from siblings by naming four related tools with their specific roles. An agent can identify the tool's scope 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 Guidelines4/5

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

Provides explicit routing to alternatives: spotify_episodes_search for episodes, spotify_shows_search for shows, spotify_search for broad queries, spotify_podcasts_show for a single show. The alternatives and their conditions are clear, but the description never states the positive condition under which THIS tool is preferred, since the listed alternatives overlap with its own scope.

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.

Resources

Need Help?