Find related artists on Spotify from an artist ID or URI, returning JSON for music discovery and recommendation workflows.
Retrieve Spotify related artists. Returns related artists from Spotify Web Player private Pathfinder responses.
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | Spotify artist ID | |
| uri | No | Spotify artist URI or open.spotify.com artist URL |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses that data comes from 'Spotify Web Player private Pathfinder responses,' indicating a non-official data source, which is useful. However, it lacks information on authentication, rate limits, side effects, or response structure.
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 two sentences, both front-loaded with the core purpose and a key detail about the data source. No extraneous information.
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?
Without an output schema, the description should explain what the returned data contains. It merely says 'returns related artists' without detailing the structure. Additionally, it does not clarify that at least one of uri or id is required.
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?
Both parameters have detailed descriptions in the input schema (100% coverage). The tool description does not add any additional semantic information about parameters, such as how to choose between uri and id or their precedence.
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 explicitly states the action ('Retrieve') and the resource ('related artists'). It distinguishes from sibling tools like spotify_artist by specifying that it returns related artists, not the artist's own details.
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 (e.g., spotify_artist_albums, spotify_artist_playlists). The description does not mention prerequisites or conditions for use.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.