Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_queue

Retrieve the current Spotify playback queue, including optional enriched details or snapshot, with configurable result limits.

Instructions

Get the current playback queue Also covers: enriched queue via describe_queue, snapshot via get_queue_snapshot — See also: describe_queue, get_queue_snapshot.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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 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"
+}
  2. First observedv1.0.1

TDQS

B3.1/5.0
Behavior2/5

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It only says 'current playback queue' and does not state whether this is a read-only operation, whether it has side effects, how it behaves with an empty queue, or what the returned queue contains. The 'Also covers' comment adds relation info but not behavioral transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately short and front-loaded with the core action, but the 'Also covers ... — See also ...' structure is awkward and somewhat redundant. It could be clearer and more linear without losing conciseness.

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?

For a simple two-parameter tool with full schema coverage, the essential mechanics are present, and the related-tool pointers add useful context. However, with no output schema and no annotations, the description does not explain what the response looks like or confirm the operation is safe, leaving an agent with some uncertainty.

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

Parameters3/5

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

Schema description coverage is 100%, so both parameters (max_results and response_format) are already documented in the input schema. The description adds no parameter-level meaning beyond what the schema provides, so the baseline of 3 is appropriate.

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 first phrase, 'Get the current playback queue,' names a specific verb and resource, so the core purpose is clear. It also calls out describe_queue and get_queue_snapshot as related alternatives, which helps differentiation, though the 'Also covers' phrasing introduces some ambiguity about whether those are capabilities of this tool or separate tools.

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

Usage Guidelines3/5

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

The description implies that enriched queue needs and snapshot needs are served by describe_queue and get_queue_snapshot, respectively, via 'Also covers' and 'See also.' However, it does not state explicit conditions for when to choose get_queue over those alternatives, leaving the routing mostly implicit.

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