Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_queue

Read-onlyIdempotent

Read the Spotify playback queue to see what's playing, what's next, total runtime, and repeated items. Includes enriched view with source context and time remaining.

Instructions

Read the playback queue. Use this for queue CONTENTS (what is playing, what is up next, how long it runs, what repeats). Use peek_next for a short lookahead. Quota: 1 read; view=enriched and include=runtime add one GET /me/player, and the context label adds one catalog read.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
viewNo'raw' (default) = the queue as returned. 'enriched' = plus the source context (playlist/album name) and total time remaining.raw
includeNoLocal analyses over the same single read, no extra request except runtime: runtime = total/avg/longest/shortest, time left on the current track, and a per-item timeline of when each row starts playing; duplicates = repeated rows and the runtime they waste; profile = unique artists/albums/shows, track-vs-episode mix, longest single-artist run.
max_resultsNoMax items to return (default: SPOTIFY_MCP_MAX_ITEMS env or 50)
response_formatNo'concise' = human prose, 'detailed' = more fields in prose, 'json' = raw API objectconcise

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv3.0.1
    • addedInput schema / properties / include
      Added value: +{
+  "default": [],
+  "description": "Local analyses over the same single read, no extra request except runtime: runtime = total/avg/longest/shortest, time left on the current track, and a per-item timeline of when each row starts playing; duplicates = repeated rows and the runtime they waste; profile = unique artists/albums/shows, track-vs-episode mix, longest single-artist run.",
+  "items": {
+    "enum": [
+      "runtime",
+      "duplicates",
+      "profile"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / view
      Added value: +{
+  "default": "raw",
+  "description": "'raw' (default) = the queue as returned. 'enriched' = plus the source context (playlist/album name) and total time remaining.",
+  "enum": [
+    "raw",
+    "enriched"
+  ],
+  "type": "string"
+}
  2. Changed2 schema fields changedv1.31.0
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
  3. Changed2 schema fields changedv1.26.1
    • addedInput schema / properties / max_results
      Added value: +{
+  "description": "Max items to return (default: SPOTIFY_MCP_MAX_ITEMS env or 50)",
+  "exclusiveMinimum": 0,
+  "maximum": 2000,
+  "type": "integer"
+}
    • addedInput schema / properties / response_format
      Added value: +{
+  "default": "concise",
+  "description": "'concise' = human prose, 'detailed' = more fields in prose, 'json' = raw API object",
+  "enum": [
+    "concise",
+    "detailed",
+    "json"
+  ],
+  "type": "string"
+}
  4. First observedv1.0.1

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly and idempotent, but the description adds real non-structured context: the read-cost quota breakdown (1 read, plus one GET /me/player for enriched/runtime, plus one catalog read for the context label). It omits return-shape details, but the quota disclosure is genuinely useful cost information.

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?

Three compact sentences, front-loaded with the core action, then scope, then alternative, then cost. No filler; every clause carries actionable information.

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 no output schema, the description adequately conveys what comes back (contents, runtime, repeats) and the cost profile. Minor gap: it doesn't hint at pagination or max_results behavior for large queues, though the schema covers the cap.

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 100%, so 3 is the baseline, but the description goes beyond the schema by tying specific parameter values (view=enriched, include=runtime, context label) to their request-cost implications, which the schema does not express.

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?

Opens with a specific verb+resource ('Read the playback queue') and immediately scopes it to queue contents (now playing, up next, runtime, repeat). It explicitly routes lookahead intent to a different tool, separating it from siblings like get_now_playing and skip_next.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

States the use case ('queue CONTENTS') and names the alternative ('Use peek_next for a short lookahead'), giving the condition that selects each. An agent can choose correctly without opening a schema.

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