Search Spotify episodes by keyword and return normalized Web Player results with limit and offset controls for building episode discovery or research workflows.
Search Spotify episodes. Returns normalized Spotify Web Player episode search results for a search term.
| Name | Required | Description | Default |
|---|---|---|---|
| q | Yes | Search term | |
| limit | No | Result limit, clamped to 1-50 | |
| offset | No | Search offset |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'returns normalized Spotify Web Player episode search results' without explaining pagination, rate limits, ordering, or what 'normalized' entails. The clamped limit behavior is in the schema but not elaborated in the description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is very concise at two sentences, with no redundant words or unnecessary information. It front-loads the action and resource effectively.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema exists, so the description should at least hint at the structure of returned data (e.g., list of episodes with metadata). It only says 'returns normalized... search results', which is vague. Given the tool's complexity and lack of annotations, the description is incomplete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so parameters are already documented. The description adds no additional meaning beyond what the schema provides (e.g., 'search term', 'offset', 'limit'). The meaning of 'q' as a search term is obvious, but no further clarification is given.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it searches Spotify episodes and returns normalized results from the Spotify Web Player. It specifies the resource ('episodes') and action ('search'), which distinguishes it from sibling tools like spotify_podcasts_search (podcasts) and spotify_shows_search (shows). However, it does not explicitly contrast with similar search tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives such as spotify_podcasts_search or spotify_search. The description lacks any context about suitable scenarios, prerequisites, or when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.