Skip to main content
Glama
khglynn

io.github.khglynn/spotify-bulk-actions-mcp

get_top_tracks

Retrieve your most played tracks from Spotify, filtered by short-term, medium-term, or long-term listening history.

Instructions

Get your top tracks based on listening history.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
time_rangeNoTime period: - "short_term": Last 4 weeks - "medium_term": Last 6 months (default) - "long_term": All timemedium_term
limitNoNumber of results (max 50)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

No annotations provided; description is minimal. For a simple read operation, it's adequate but doesn't disclose authentication requirements or output behavior.

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?

Extremely concise one-sentence description with no filler; front-loaded with the core purpose.

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?

With output schema present and clear parameter schema, the description is sufficient for this simple tool; minor omission is explanation of return values.

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

Parameters3/5

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

Input schema has 100% coverage with clear parameter descriptions; description adds no extra meaning beyond 'get your top tracks'.

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?

Description clearly states the tool retrieves top tracks based on listening history, which is specific and distinct from siblings like get_top_artists or get_recently_played.

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

Usage Guidelines2/5

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. Could mention it's for personal listening history as opposed to curated playlists or artist data.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/khglynn/spotify-bulk-actions-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server