Skip to main content
Glama
Sign In
Spotify MCP Server

Spotify MCP Server

by jamiew
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Add to Queue

add_to_queue

Add a track or podcast episode to the Spotify playback queue by providing a track ID, Spotify URI, or open.spotify.com URL.

Instructions

Add a track or podcast episode to the playback queue.

Args:
    track_id: Track ID, or a spotify:track:/spotify:episode: URI or
        open.spotify.com URL. A bare ID is taken as a track.
Returns:
    Status and message

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": {
      "track_id": "<track_id>"
    },
    "name": "add_to_queue"
  }
}

Input Schema

NameRequiredDescriptionDefault
track_idYes

Output Schema

NameRequiredDescriptionDefault
statusYes
messageYes
snapshot_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.3.1
    • removedOutput schema / additionalProperties
      Removed value: -{
-  "type": "string"
-}
    • addedOutput schema / description
      Added value: +"Result of a state-changing operation."
    • addedOutput schema / properties
      Added value: +{
+  "message": {
+    "title": "Message",
+    "type": "string"
+  },
+  "snapshot_id": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null,
+    "title": "Snapshot Id"
+  },
+  "status": {
+    "title": "Status",
+    "type": "string"
+  }
+}
    • addedOutput schema / required
      Added value: +[
+  "status",
+  "message"
+]
    • changedOutput schema / title
      Previous value: -"add_to_queueDictOutput"New value: +"ActionResult"
  2. Addedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false and openWorldHint=true, so the mutation profile is covered by structured data. The description adds useful input-flexibility context (bare IDs, Spotify URIs, open.spotify.com URLs), but it omits the important behavioral precondition that Spotify requires an active device and that repeat calls enqueue duplicates.

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 purpose sentence is front-loaded and the arg explanation is tight and specific. The 'Returns: Status and message' line is low-value boilerplate given an output schema exists, but overall there is little waste.

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?

With an output schema present, the return-value line is unnecessary, and the real gaps are behavioral: no mention of requiring an active device, no note on deduplication, and no contrast with sibling tools. For a single-parameter mutation tool this is adequate but leaves out context an agent needs to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the single property 'track_id' carries no description, so the description must compensate — and it does, explaining accepted forms (bare ID, spotify:track:/spotify:episode: URI, open.spotify.com URL) and the default that a bare ID is treated as a track. That is a meaningful addition 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?

The description states a specific verb and resource — 'Add a track or podcast episode to the playback queue' — so an agent knows exactly what is created and where. It does not distinguish itself from plausible siblings like add_tracks_to_playlist or control_playback, which is the only thing keeping it from a 5.

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 exclusion of alternatives; the phrase 'playback queue' only implicitly contrasts with playlist tools. An agent must infer on its own whether queueing a track differs from adding it to a playlist, and nothing is said about prerequisites such as an active playback device.

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