Retrieve Spotify album metadata and track listings by album ID or open.spotify.com URL, with optional track limit and offset.
Retrieve Spotify album details. Returns normalized Spotify Web Player album metadata and tracks from private Pathfinder responses.
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | Spotify album ID | |
| uri | No | Spotify album URI or open.spotify.com album URL | |
| limit | No | Track limit, clamped to 1-50 | |
| offset | No | Track offset |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Without annotations, the description fails to disclose behavioral traits such as authentication requirements, rate limits, side effects, or error handling. 'Private Pathfinder responses' is unclear.
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 concise with two sentences. However, 'private Pathfinder responses' adds unnecessary jargon without explanation.
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 detail return structure. It only mentions 'metadata and tracks' vaguely. Also, all parameters optional but no defaults or behavior specified when none provided.
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 the schema already documents all parameters. The description adds no extra meaning beyond what is in the schema, meeting the baseline.
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 retrieves Spotify album details and mentions returning metadata and tracks, distinguishing it from sibling tools like spotify_album_tracks. However, 'private Pathfinder responses' is vague and could be confusing.
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_album_tracks or spotify_albums_search. Missing when-not-to-use and context for parameter selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.