Skip to main content
Glama
Sign In
Spotify Data MCP Server

Spotify Data MCP Server

by eduair94
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get playlist

get_playlist
Read-onlyIdempotent

Retrieve a Spotify playlist's name, owner, followers, description, and tracks with lifetime play counts. Use offset and limit to page through long playlists.

Instructions

A playlist's name, owner, followers and description, plus limit tracks (max 100) from offset with lifetime play counts. Use next_offset from the answer to page through long playlists (later pages skip the metadata and cost one request).

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": {
      "playlist": "<playlist>"
    },
    "name": "get_playlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoTracks to return (1-100).
offsetNoIndex of the first track (0 = start).
playlistYesSpotify playlist id, spotify:playlist:<id> URI or open.spotify.com/playlist/<id> URL.
include_play_countsNoAdd each track's lifetime play count.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.1/5.0
Behavior4/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 genuinely new behavioral detail beyond them: that only 100 tracks can be returned at once, that later pages omit metadata, and that each page costs one request — useful for planning call sequences.

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, no filler. The returned fields come first and the paging instruction follows, so the most important operational detail is easy to find.

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

Completeness5/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 carries the burden of describing returns and does so: metadata fields, the track window, play counts, and the next_offset continuation token. Nothing an agent needs in order to call and paginate this tool is missing.

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 limit, offset, playlist and include_play_counts are already documented in structured fields. The description adds only marginal meaning beyond that — restating the 100-track cap and introducing next_offset, which is a return value rather than an input. 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 concretely enumerates what the tool returns (playlist name, owner, followers, description, a window of tracks with lifetime play counts), which makes the resource unmistakable. It does not explicitly contrast itself with siblings such as get_tracks or search, but the resource scope is specific enough that an agent can tell what it does.

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

Usage Guidelines4/5

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

It gives clear operational guidance for the paging case: use next_offset from the response to continue, and notes that later pages skip metadata and cost one request. There is no guidance on when to prefer this over search or get_tracks, but the within-tool usage context is explicit.

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