Spotify MCP Server

by jamiew

Overview Schema Source Related Servers Discussions Admin

Python

Local

Get Queue

get_queue

Read-onlyIdempotent

Retrieve the currently playing track and upcoming tracks from the Spotify playback queue.

Instructions

Get the current playback queue. Returns: Currently playing track and queue of upcoming tracks

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_queue"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`queue`	Yes
`currently_playing`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.8.1Nov 4, 2026

addedOutput schema / $defs / Track / properties / show

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Show"
+}

addedOutput schema / $defs / Track / properties / show_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Show Id"
+}

addedOutput schema / $defs / Track / properties / type

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Type"
+}

Changed6 schema fields changedv0.6.1Sep 17, 2026

addedOutput schema / $defs / Track / properties / id / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / $defs / Track / properties / id / default
```
Added value: +null
```
removedOutput schema / $defs / Track / properties / id / type
```
Removed value: -"string"
```

addedOutput schema / $defs / Track / properties / is_local

Added value: +{
+  "default": false,
+  "title": "Is Local",
+  "type": "boolean"
+}

addedOutput schema / $defs / Track / properties / played_at

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Played At"
+}

changedOutput schema / $defs / Track / required

Previous value: -[
-  "name",
-  "id",
-  "artist"
-]New value: +[
+  "name",
+  "artist"
+]

Changed5 schema fields changedv0.3.1Jun 2, 2026

addedOutput schema / $defs

Added value: +{
+  "Track": {
+    "description": "A Spotify track with metadata.",
+    "properties": {
+      "added_at": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Added At"
+      },
+      "album": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Album"
+      },
+      "album_id": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Album Id"
+      },
+      "artist": {
+        "title": "Artist",
+        "type": "string"
+      },
+      "artists": {
+        "anyOf": [
+          {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Artists"
+      },
+      "duration_ms": {
+        "anyOf": [
+          {
+            "type": "integer"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Duration Ms"
+      },
+      "external_urls": {
+        "anyOf": [
+          {
+            "additionalProperties": {
+              "type": "string"
+            },
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "External Urls"
+      },
+      "id": {
+        "title": "Id",
+        "type": "string"
+      },
+      "name": {
+        "title": "Name",
+        "type": "string"
+      },
+      "popularity": {
+        "anyOf": [
+          {
+            "type": "integer"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Popularity"
+      },
+      "release_date": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Release Date"
+      }
+    },
+    "required": [
+      "name",
+      "id",
+      "artist"
+    ],
+    "title": "Track",
+    "type": "object"
+  }
+}

addedOutput schema / description

Added value: +"Currently playing track plus the upcoming queue."

addedOutput schema / properties

Added value: +{
+  "currently_playing": {
+    "anyOf": [
+      {
+        "$ref": "#/$defs/Track"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null
+  },
+  "queue": {
+    "items": {
+      "$ref": "#/$defs/Track"
+    },
+    "title": "Queue",
+    "type": "array"
+  }
+}

addedOutput schema / required
```
Added value: +[
+  "queue"
+]
```

changedOutput schema / title

Previous value: -"get_queueDictOutput"New value: +"QueueState"

Addedv1.0.0Jan 2, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds useful context about the shape of the response (currently playing track and upcoming tracks), but says nothing about behavior when no device is active or when the queue is empty, which is the main failure mode an agent would want to anticipate.

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?

Two short lines with the core action front-loaded and the return contents immediately after. The awkward 'Returns:' indentation adds a little noise but nothing is wasted or buried.

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 zero parameters and an output schema present, the definition covers nearly everything an agent needs to invoke it correctly. The one gap is the lack of any note about authentication scope or behavior without an active device, which matters for an open-world playback tool.

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?

The tool takes zero parameters, so the baseline of 4 applies; there is nothing for the description to disambiguate. No parameter-level meaning is missing because no parameters exist.

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?

States a specific verb and resource ("Get the current playback queue") and clarifies scope by listing what is returned: the currently playing track plus upcoming tracks. It does not differentiate from the close sibling get_playback_state, which returns overlapping playback information, so an agent must still infer the boundary.

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 guidance on when to use this versus alternatives such as get_playback_state (current track/device/progress) or add_to_queue, nor any note on prerequisites like an active playback session. The only implicit signal is that it returns upcoming tracks, which is left for the agent to interpret.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server