Skip to main content
Glama
Sign In
Spotify Data MCP Server

Spotify Data MCP Server

by eduair94
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Track genres, moods and BPM

get_track_insights
Read-onlyIdempotent

Retrieve genres, moods, activities, tempo, credits, lyric flags, and vocal languages for up to 50 Spotify tracks to analyze or classify them.

Instructions

Genres, moods and activities (with Spotify's 0-1 weights), tempo in BPM, credits (writers, producers), lyrics flag and vocal languages for up to 50 tracks.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tracks": "<tracks>"
    },
    "name": "get_track_insights"
  }
}

Input Schema

NameRequiredDescriptionDefault
tracksYesSpotify track ids, spotify:track:<id> URIs or open.spotify.com/track/<id> URLs (1-50).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds real value by naming the returned fields and clarifying that Spotify's weights are on a 0-1 scale, but it says nothing about missing credits, partial failures, or latency for a 50-track batch.

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

Conciseness4/5

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

A single dense sentence with zero filler, leading with the most distinctive fields (genres and moods). It reads as a fragment rather than a statement of action, which costs a little clarity but wastes no words.

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 no output schema, the description correctly carries the burden by listing the returned data shapes. The main residual gap is absence of any error or empty-result behavior for invalid or unavailable track ids.

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?

Schema coverage is 100% and the tracks parameter already documents accepted id/URI/URL forms and the 1-50 range, so the description only restates the cap. Baseline 3 is appropriate since the schema does the heavy lifting.

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

Purpose4/5

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

The description enumerates the specific payload (genres, moods, activities, tempo, credits, lyrics flag, vocal languages), so an agent knows exactly what data comes back. It stops short of a verb and never contrasts itself with the sibling get_tracks, which returns basic metadata, so the boundary between the two must be inferred from the name alone.

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?

There is no when-to-use guidance, no prerequisite statement, and no pointer to an alternative such as get_tracks for plain metadata or search for discovering track ids. The 50-track cap is the only usage-shaped constraint, and it duplicates the schema.

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

Deploy Server

Other Tools