Skip to main content
Glama
Sign In
Spotify Data MCP Server

Spotify Data MCP Server

by eduair94
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get album

get_album
Read-onlyIdempotent

Fetch a Spotify album's track list, lifetime play counts, release date, label, UPC, and popularity using an album ID or URL.

Instructions

An album with its track list and (by default) every track's lifetime play count, plus the album total, release date, label, UPC and popularity.

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": {
      "album": "<album>"
    },
    "name": "get_album"
  }
}

Input Schema

NameRequiredDescriptionDefault
albumYesSpotify album id, spotify:album:<id> URI or open.spotify.com/album/<id> URL.
include_play_countsNoAdd each track's lifetime play count and the album total.

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 openWorld, so the safety profile is covered. The description adds the meaningful behavioral fact that per-track lifetime play counts and an album total are returned by default, but says nothing about failure behavior for a bad album id or the external Spotify lookup implied by openWorldHint.

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 efficient sentence that front-loads the track list and the default play-count behavior, with no filler. The only structural weakness is that it is a fragment describing output rather than an action statement.

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 and only two parameters, the description carries the return-value burden well, enumerating track list, play counts, album total, release date, label, UPC and popularity. What remains missing is routing guidance relative to sibling tools, not return detail.

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%, so both parameters are already documented. The description restates the include_play_counts default and clarifies that 'play count' means lifetime plays at both track and album level, which is a small but genuine addition — baseline 3 is appropriate.

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 clearly identifies the resource and its contents (album with track list, per-track play counts, total, release date, label, UPC, popularity), so an agent can infer it retrieves album detail. However, it is written as a return-value noun phrase with no explicit verb and makes no reference to siblings like get_tracks or search, so differentiation is left to the name.

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 or when-not-to-use guidance, and no alternatives named despite a crowded sibling set (get_tracks, get_track_play_count, search, get_artist_overview). The only hint is the parenthetical '(by default)' about play counts, which describes output rather than selection criteria.

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