Search Spotify artists by term to retrieve normalized Web Player artist results with limit and offset pagination.
Search Spotify artists. Returns normalized Spotify Web Player artist 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, so description must disclose behavior. It mentions 'normalized' results but does not describe the response structure, data freshness, or any side effects. Lacks details important for an agent to predict outcomes.
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?
Very concise, one sentence with essential verb and object. Front-loaded with action. However, it could benefit from additional context without sacrificing brevity.
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, so description should explain return values. It only says 'artist search results' without structure or other details like pagination hints (despite offset/limit parameters missing behavioral context). Incomplete for effective tool use.
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?
Input schema has 100% description coverage, so baseline is 3. The description adds no extra meaning beyond the schema (e.g., no clarification on offset behavior beyond 'search offset').
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?
Clearly states it searches for Spotify artists and returns normalized Web Player search results. The verb 'search' and resource 'Spotify artists' are specific. It distinguishes from sibling tools like spotify_search or spotify_tracks_search by focusing on artists.
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 alternatives like spotify_search or spotify_artist. The description does not mention exclusions or preferred contexts.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.