Crawlora MCP

spotify_shows_search

Read-only

Search Spotify Web Player podcast shows by title or keyword and return show profiles and IDs. Use spotify_podcasts_search for the broader podcast search surface or a returned show ID for episode/detail tools.

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_shows_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

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description usefully adds that it returns profiles and IDs and that IDs chain into detail tools, but it says nothing about pagination/limit behavior, result shape, or rate limits beyond what the schema already exposes.

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?

Two sentences, front-loaded with the primary action and return value, then the routing guidance. No filler; every clause earns 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?

An output schema exists, so return values need not be spelled out, and the description covers the chaining path to detail tools. For an 11-param search tool it is largely complete, though it could say more about the multi-section result structure implied by the include* flags.

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% with 11 well-documented parameters, so the schema carries the parameter burden. The description only loosely hints at searchTerm ('by title or keyword') and adds no meaning for the include*/limit/offset flags, so the baseline 3 applies.

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?

States a specific verb (Search) and resource (Spotify podcast shows) and the return surface (show profiles and IDs), and it names the sibling spotify_podcasts_search. The differentiation is present but the phrase 'broader podcast search surface' is fuzzy about what the sibling actually adds, so it falls just short of a clean 5.

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 explicitly routes the agent: use spotify_podcasts_search for a broader surface, or feed a returned show ID into episode/detail tools. That is clear alternative-naming, though the selecting condition ('broader') is not crisply defined and there is no explicit when-not-this-tool statement.

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.