Skip to main content
Glama
Sign In
Spotify MCP Server

Spotify MCP Server

by EvansLR
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

spotify_get_current_playback

Fetch the current Spotify playback state, including the active track, progress, and device details, to monitor or act on what's playing.

Instructions

获取当前播放状态，包括当前歌曲、播放进度、设备等信息

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": "spotify_get_current_playback"
  }
}

Input Schema

NameRequiredDescriptionDefault
device_idNo设备ID（可选）

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description must carry the burden of disclosing side effects and requirements. It implies a read-only operation via 'get', but does not explicitly state that it is non-destructive, whether authentication is required, or what errors may occur.

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?

The description is a single, focused sentence that immediately states the action and key result fields. No unnecessary words or redundancy.

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?

The description covers the core purpose and expected data, but lacks context around authentication prerequisites, error conditions, and how the optional device_id parameter behaves in different scenarios. Given no output schema and no annotations, a few more contextual details would improve completeness.

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?

The schema already covers the only parameter (device_id) with a minimal description. The tool description adds no extra meaning about how device_id affects the response, but schema coverage is complete, so a baseline of 3 is appropriate.

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 identifies the resource (current playback state) and the action (get), and specifies the key information included (current song, progress, device). This distinguishes it from sibling tools like pause, next, or get_devices.

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?

The description provides no guidance on when to use this tool versus alternatives, nor does it mention prerequisites such as authentication. Sibling tools exist for auth and playback control, but the description does not position this tool relative to them.

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