Skip to main content
Glama
jamiew

Spotify MCP Server

by jamiew
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Add to Queue

add_to_queue

Add a track to your Spotify playback queue by providing its track ID, URI, or URL. Solves the need to queue music directly without interrupting current playback.

Instructions

Add a track to the playback queue.

Args:
    track_id: Track ID, spotify:track: URI or open.spotify.com URL
Returns:
    Status and message

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
track_idYes

Output Schema

TableJSON 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

A3.9/5.0
Behavior3/5

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

Annotations already indicate this is a mutating, non-idempotent operation. The description adds that it targets the playback queue and returns a status/message, but it does not disclose likely failure conditions (e.g., no active device) or the effect of repeated calls. No contradiction with annotations exists.

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?

The description is concise and front-loaded, with a clear action statement followed by compact Args and Returns sections. Every line adds useful information and there is no redundant prose.

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?

For a one-parameter tool with an output schema, the description covers accepted input formats and summarizes the return value well. It could mention edge cases like requiring an active playback device, but the core invocation information is complete.

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

Parameters5/5

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

The input schema provides only a raw string property with zero description coverage chosen. The description explicitly defines the accepted formats: track ID, spotify:track URI, or open.spotify.com URL, which is essential and fully compensates for the schema gap.

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

Purpose5/5

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

The description states a specific action ('Add') and a specific resource ('the playback queue'), clearly distinguishing it from playlist-focused siblings like add_tracks_to_playlist. There is no ambiguity about what the tool operates on.

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?

The description gives no guidance on when to use this tool over alternatives, no exclusions, and no prerequisites such as requiring an active playback device or authentication context. It only restates the action itself, leaving selection entirely to inference.

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