Search Spotify shows by keyword and return normalized Web Player results, with limit and offset for paging.
Search Spotify shows. Returns normalized Spotify Web Player show 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?
No annotations provided; the description only states it searches and returns normalized results. It does not disclose authentication needs, rate limits, pagination behavior, or what 'normalized' means, leaving significant behavioral gaps.
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?
Two sentences, no wasted words. It is concise but could be slightly more informative without being verbose.
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?
Despite 100% schema coverage and no output schema, the description lacks details on return format or normalization. For a simple search tool with pagination parameters, it is minimally complete but could be improved.
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 description coverage is 100% with parameter descriptions for 'q', 'offset', and 'limit'. The description adds no additional meaning beyond the schema (e.g., 'search term' is already in schema), so baseline score of 3 applies.
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 shows and returns normalized results from the Spotify Web Player. The verb 'search' and resource 'shows' are specific, and it is distinguishable from general 'spotify_search' but could differentiate more from 'spotify_podcasts_search'.
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 on when to use this tool versus sibling tools like 'spotify_podcasts_search' or 'spotify_search'. The purpose is implied but no exclusions or alternatives are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.