Skip to main content
Glama
Sign In
Spotify Data MCP Server

Spotify Data MCP Server

by eduair94
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related artists

get_related_artists
Read-onlyIdempotent

Return artists Spotify lists as related to a given artist, including "Fans also like" suggestions and an optional limit of 1–20.

Instructions

Artists Spotify lists as related to ("Fans also like") the given artist.

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": {
      "artist": "<artist>"
    },
    "name": "get_related_artists"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many related artists to return (1-20).
artistYesSpotify artist id, spotify:artist:<id> URI or open.spotify.com/artist/<id> URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnly, idempotent, non-destructive and open-world, so safety behavior is covered. The description adds one genuinely useful nuance — these are Spotify's curated 'Fans also like' relations rather than a computed similarity — but says nothing about ordering, empty results, or behavior for an unknown artist, so with annotations the bar is only modestly cleared.

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 front-loaded sentence with no wasted words and the key differentiator ('Fans also like') placed in parentheses for immediate recognition. It is tight to the point of leaving no room for the context an agent might want, but nothing in it is redundant.

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

Completeness3/5

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

For a two-parameter read with full schema coverage, no output schema and complete safety annotations, the description is adequate but thin — it never indicates what a returned item looks like (artist names/ids usable in other tools) or how results are ordered, which an agent must infer.

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%: both the artist identifier formats (id, URI, URL) and the limit range (1–20, default 20) are fully documented in the schema. The description adds no meaning beyond 'the given artist', so the baseline of 3 applies.

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?

Names the exact resource retrieved (artists Spotify lists as related, 'Fans also like') and ties it to the given artist, so the agent knows precisely what comes back. It is meaningfully distinguishable from siblings like get_artist_overview or get_artist_insights by the word 'related', though it never explicitly contrasts itself with them.

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

Usage Guidelines3/5

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

Usage is only implied by the name and one-liner: call it when you want a given artist's related artists. There is no statement of when to prefer get_artist_overview / get_artist_insights over this, nor any prerequisite or exclusion.

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