Fetch Spotify artist details via ID or URI. Delivers normalized Web Player overview data from private Pathfinder responses for your applications.
Retrieve Spotify artist details. Returns normalized Spotify Web Player artist overview data from 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?
With no annotations, the description must disclose behavioral traits. It states 'Retrieve' implying a read operation, but does not mention authentication, rate limits, error handling, or what happens if the artist is not found. The vague reference to 'private Pathfinder responses' adds no clarity.
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 short sentences with no wasted words. It could be slightly improved by front-loading the purpose more explicitly, but it is already concise.
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?
Given no output schema, the description should hint at the return structure. It only says 'normalized Spotify Web Player artist overview data', which is vague. It does not mention key fields, pagination, or error conditions, making it incomplete for a tool with no output schema.
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 clear descriptions for uri and id. The description does not add further meaning beyond the schema, such as how to choose between parameters or what happens if both are provided. Baseline 3 is appropriate.
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 'Retrieve Spotify artist details' and specifies the data source (normalized Spotify Web Player artist overview data from private Pathfinder responses). However, it does not explicitly differentiate from sibling tools like spotify_artist_albums or spotify_artist_playlists, but the mention of 'overview data' implies a general artist info endpoint.
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?
The description provides no guidance on when to use this tool versus alternatives (e.g., spotify_artist_albums, spotify_artist_related). There is no mention of when to use it or when not to use it, which is a significant gap given the many sibling tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.