Retrieve your most-listened-to Spotify artists by time range: short term (4 weeks), medium term (6 months default), or long term (years).
Get the user's most-listened-to artists. time_range: short_term (~4 weeks), medium_term (~6 months, default), or long_term (years).
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| time_range | No | medium_term |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of explaining behavior. It clearly explains time_range semantics and defaults, and 'Get' implies a read-only intent. It does not mention limitation, pagination, or response behavior, but for a simple read-only list tool the core behavior is disclosed.
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 compact and front-loaded, delivering the core action in the first sentence and then the most important parameter detail in the second. Every sentence adds value with no repetition or padding.
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?
The tool is simple, has an output schema, and the description provides enough context to call it correctly for the main parameter. The only minor gap is not mentioning limit in prose, but its default is present in the input 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 0%, so the description must compensate. It fully explains time_range's meaning and valid values, including the default. The limit parameter is left to its schema default, but the tool's core semantics are conveyed by the description.
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 uses a specific verb ('Get') with a clear resource ('the user's most-listened-to artists') and clearly differentiates it from sibling tools like top_tracks. The time_range semantics strengthen clarity about what kind of result is returned.
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 gives clear context for when to use this tool: it returns the user's top listened-to artists across supported periods. It does not explicitly name alternatives or exclusions, but the 'most-listened-to artists' framing makes its use case obvious relative to top_tracks and recently_played.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.