mcp-spotify

by obrien-matthew

Overview Schema Source Related Servers Discussions Admin

Python

Local

get_my_top_tracks

Retrieve your top Spotify tracks over a custom time range. Use this data to seed personalized playlists.

Instructions

Get the current user's top tracks on Spotify.

time_range options:

"short_term": approximately last 4 weeks
"medium_term": approximately last 6 months (default)
"long_term": all time

Useful as a seed for building personalized playlists.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_my_top_tracks"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`time_range`	No		medium_term

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Jul 29, 2026

TDQS

A4.4/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full disclosure burden. It explains the time_range options with approximate durations and implies personalization (current user's top tracks). It does not detail return format, but an output schema exists to fill that gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise: two short paragraphs and a bullet list. It front-loads the core purpose and provides parameter details efficiently without extraneous text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of an output schema (not shown), the description does not need to explain return values. It covers parameter semantics and a use case, making it sufficient for a simple retrieval tool. It could mention that results are user-specific, but the name implies this.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 2 parameters with 0% description coverage. The description adds meaning to 'time_range' by listing valid values and their meanings, but does not add information for 'limit' beyond the schema's default.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's function: 'Get the current user's top tracks on Spotify.' It distinguishes itself from siblings like 'get_my_top_artists' by specifying 'tracks' and from search tools by emphasizing 'top tracks' based on user listening history.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly mentions a use case: 'Useful as a seed for building personalized playlists.' However, it does not provide explicit when-not-to-use guidance or compare with alternatives like 'get_saved_tracks' or 'get_my_top_artists'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.