Skip to main content
Glama
Sign In
Spotify Data MCP Server

Spotify Data MCP Server

by eduair94
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Artist monthly listeners and stats

get_artists_stats
Read-onlyIdempotent

Fetch monthly listeners, followers, world rank, popularity, genres, and top city listener counts for up to 50 Spotify artists in one call.

Instructions

Monthly listeners, followers, world rank, popularity, genres and top 5 cities (with listener counts) for up to 50 artists in one call.

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": {
      "artists": "<artists>"
    },
    "name": "get_artists_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
artistsYesSpotify artist ids, spotify:artist:<id> URIs or open.spotify.com/artist/<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 readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is covered. The description adds the batch ceiling and the shape of the city data, but says nothing about behavior for invalid or unknown artist IDs, partial failures, or rate limits, which is where extra context would have earned credit.

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?

One sentence, front-loaded with the returned metrics and ending with the batch limit. The metric list is a justified enumeration for a stats tool, though it reads as a flat comma list rather than a structured list of what each artist object contains.

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?

There is no output schema, so the description must carry the return-value burden and it does so by naming every reported field including the top-5-cities detail. Remaining gaps are the per-artist result structure and handling of artists with no data, which are minor for a single-parameter read tool.

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 single parameter already documents the accepted ID/URI/URL formats and the 1-50 bounds. The description's 'up to 50 artists' merely restates maxItems, adding no meaning beyond the schema.

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 names a specific resource and enumerates the exact metrics returned (monthly listeners, followers, world rank, popularity, genres, top 5 cities), so an agent knows precisely what data it gets. It does not distinguish itself from close siblings such as get_artist_overview or get_artist_insights, which is the main clarity gap.

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 and no named alternative. The phrase 'in one call' and 'up to 50 artists' weakly implies a batch use case, but an agent choosing between this and get_artist_overview/get_artist_insights is left to guess.

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