Skip to main content
Glama
Sign In
Spotify Data MCP Server

Spotify Data MCP Server

by eduair94
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Artist genres, moods and BPM

get_artist_insights
Read-onlyIdempotent

Retrieves sound profiles for up to 20 artists from their top tracks, including genres, moods, activity weights (0–1), and average, minimum, and maximum BPM.

Instructions

An artist's sound profile from their top tracks: genres, moods and activities with 0-1 weights, and tempo (average, min, max BPM). Up to 20 artists per 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_artist_insights"
  }
}

Input Schema

NameRequiredDescriptionDefault
artistsYesSpotify artist ids, spotify:artist:<id> URIs or open.spotify.com/artist/<id> URLs (1-20).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and non-destructive, so safety is covered. The description adds genuinely new behavioral context: values are computed from top tracks (an aggregate, not the full catalogue) and weights are normalized 0-1. It omits what happens for unknown artists or artists with sparse data.

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?

Two sentences, zero filler, and the return payload is front-loaded before the batch-size note. Every clause carries information.

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 takes on the burden of explaining return values, and it does so well by naming genres, moods, activities with 0-1 weights, and average/min/max tempo. Remaining gaps are edge-case behavior for missing or ambiguous artist inputs.

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 description coverage is 100%, and the schema already documents the accepted ID/URI/URL formats and the 1-20 bounds. The description's 'Up to 20 artists per call' merely restates maxItems, adding no new 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?

Specific verb-less but precise statement of what is returned: a sound profile of genres, moods, activities and BPM derived from an artist's top tracks. It is clearly distinguishable in content from get_artist_overview or get_artists_stats, though it never names a sibling to contrast with.

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 explicit when-to-use guidance and no alternatives are named, even though the sibling list contains several artist-focused tools (get_artist_overview, get_artists_stats, get_related_artists) an agent must choose between. Usage is only inferable from the phrase 'from their top tracks'.

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