Skip to main content
Glama
Sign In
spotify-mcp

spotify-mcp

by jmbluhm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

SpotifyPlaylist

Create, update, and manage Spotify playlists: list user playlists, view tracks, add or remove tracks, and change playlist details.

Instructions

Manage Spotify playlists. - get: Get a list of user's playlists. - get_tracks: Get tracks in a specific playlist. - add_tracks: Add tracks to a specific playlist. - remove_tracks: Remove tracks from a specific playlist. - change_details: Change details of a specific playlist. - create: Create a new playlist.

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": {
      "action": "<action>"
    },
    "name": "SpotifyPlaylist"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoName for the playlist (required for create and change_details).
actionYesAction to perform: 'get', 'get_tracks', 'add_tracks', 'remove_tracks', 'change_details', 'create'.
publicNoWhether the playlist should be public (for create action).
track_idsNoList of track IDs to add/remove.
descriptionNoDescription for the playlist.
playlist_idNoID of the playlist to manage.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While it lists six actions and their basic purposes, it doesn't disclose critical behavioral traits: authentication requirements, rate limits, whether operations are destructive, what happens on errors, or what the return values look like. For a multi-action tool with potential write operations (add, remove, change, create), this is a significant gap in transparency.

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?

The description is efficiently structured with a brief overview followed by a bulleted list of actions. Each bullet is concise and to the point. However, the opening 'Manage Spotify playlists' is redundant with the tool name and could be eliminated, and the bullet format while clear isn't the most natural language for AI comprehension.

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

Completeness2/5

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

For a complex multi-action tool with six parameters and no annotations or output schema, the description is incomplete. It doesn't explain return values, error conditions, authentication requirements, or the relationships between actions. The tool handles both read and write operations, but the description provides minimal behavioral context, making it inadequate for safe and effective use.

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 the schema already documents all six parameters thoroughly. The description doesn't add any meaningful parameter semantics beyond what's in the schema - it simply lists action names without explaining parameter dependencies or constraints. The baseline of 3 is appropriate when the schema does all the parameter documentation work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Manage Spotify playlists' which is a vague purpose that doesn't specify what management entails. It then lists six sub-actions with brief explanations, but the overall purpose remains broad. While it distinguishes from sibling tools by focusing on playlists rather than search, playback, or queue operations, the verb 'manage' is too generic for clear understanding.

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?

No guidance is provided about when to use this tool versus the sibling tools (SpotifyGetInfo, SpotifyPlayback, SpotifyQueue, SpotifySearch). The description lists six actions but doesn't explain when each should be used relative to each other or to other tools. There's no mention of prerequisites, authentication requirements, or contextual factors that would guide selection.

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