Spotify MCP Server

Overview Schema Source Related Servers Discussions Admin

Now Playing

get_playback_state

Read-onlyIdempotent

Retrieves the current Spotify playback state, including track, device, progress, shuffle, and repeat, so you can check what is playing and whether playback is active.

Instructions

Get the current playback state: track, device, progress, shuffle and repeat.

Returns:
    PlaybackState (is_playing is False when nothing is playing)

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Default
`track`	No
`device`	No
`repeat`	No	off
`volume`	No
`shuffle`	No
`is_playing`	Yes
`progress_ms`	No
`currently_playing_type`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 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"
+}

addedOutput schema / properties / currently_playing_type

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

Addedv0.6.1Sep 17, 2026

TDQS

A4.2/5.0

Behavior4/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 a genuinely useful behavioral detail beyond that: is_playing is False when nothing is playing, which tells the agent how to interpret the empty/none state. It stops short of noting auth or active-device requirements, keeping it from a 5.

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?

One sentence for purpose, one line for the return edge case, nothing else. The field list is front-loaded and every phrase carries information the agent needs; no restatement of the title or name.

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 zero-parameter read tool with an output schema present, the definition covers purpose, returned fields and the empty-state semantics, which is nearly everything needed to call it correctly. The remaining gap is environmental context (active device / account tier) that determines whether playback state is even available.

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 there is nothing for the description to disambiguate and the baseline of 4 applies. The schema is an empty object, consistent with the description's parameterless framing.

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?

States a specific verb and resource ("Get the current playback state") and enumerates exactly what comes back: track, device, progress, shuffle, repeat. That enumeration distinguishes it cleanly from control_playback (mutation) and get_queue (upcoming items) without either sibling being named.

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?

Usage is only implied: an agent can infer this answers "what is playing right now." There is no explicit guidance on when to prefer it over get_queue or list_devices, and no mention of prerequisites such as an active device or premium account, which materially affect whether this call returns useful data.

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

Deploy Server