Skip to main content
Glama
jamiew

Spotify MCP Server

by jamiew
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

Get Queue

get_queue
Read-onlyIdempotent

Retrieve the current playback queue, showing the currently playing track and the list of upcoming tracks.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
currently_playingNo
queueYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed5 schema fields changedv0.3.1
    • 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"
  2. Addedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint. The description adds minimal behavioral detail (returns current and upcoming tracks) but does not contradict annotations. Adequate but not enhanced.

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?

Extremely concise: two sentences, front-loaded with the main action, and no wasted words.

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?

Given zero parameters, informative annotations, and an output schema, the description is sufficient for a simple read operation. It explicitly states the return content, fulfilling basic needs.

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?

No parameters exist (0 params, 100% schema coverage). The description is not required to add parameter info, and it correctly omits irrelevant details.

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 clearly states the tool retrieves the current playback queue and specifies the return content (currently playing and upcoming tracks). It distinguishes itself from sibling tools like add_to_queue or playback_control.

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 on when to use this tool versus alternatives like get_playlist_tracks or search_tracks. The description lacks context for selective invocation.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jamiew/spotify-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server