Spotify MCP Server

Overview Schema Source Related Servers Discussions Admin

get_currently_playing

Retrieve the track or episode currently playing on your Spotify account. Get live playback details without interrupting your listening.

Instructions

Get the currently playing track or episode.

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_currently_playing"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1May 5, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations provided, so description carries full burden. Merely states 'get currently playing track or episode' without disclosing that it may return null if nothing is playing, or that it requires an active playback session. Lacks details on auth needs, error scenarios, or side effects.

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?

Single sentence, no wasted words. Efficiently communicates the tool's purpose.

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?

Has an output schema (not shown) but no requirement to describe returns. However, description lacks context about tool validity (e.g., requires active device, returns null if nothing playing). Does not compensate for missing annotations or usage guidance. Adequate but incomplete for a straightforward 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?

Input schema has zero parameters with 100% schema description coverage. Description does not add parameter info but none is needed. Baseline score is high for no-parameter tools, though description could clarify if optional context is implied (none evident).

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?

Description clearly states the tool retrieves the currently playing track or episode. It is specific about the resource (currently playing item) and verb (get). However, it does not explicitly differentiate from the sibling tool 'get_playback_state', which provides broader playback status.

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_playback_state'. Does not mention prerequisites (e.g., active playback, device) or when to expect null results. The description provides no usage context.

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