Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_currently_playing

Retrieve the current Spotify track or episode with playback progress. Lightweight poll—use the full-state endpoint for shuffle, device, and volume.

Instructions

Lightweight poll of what is playing right now: the item and progress only. For full session state (shuffle/repeat mode, active device, volume) use get_now_playing instead. Also covers: get_now_playing full-state poll — See also: get_now_playing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
marketNoISO 3166-1 alpha-2 country code — localises item names; lowercase input is uppercased; defaults to the account market
response_formatNo'concise' = human prose, 'detailed' = more fields in prose, 'json' = raw API objectconcise
additional_typesNoItem types to include in the response. Default: ['track', 'episode']

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.26.1
    • addedInput schema / properties / additional_types
      Added value: +{
+  "default": [
+    "track",
+    "episode"
+  ],
+  "description": "Item types to include in the response. Default: ['track', 'episode']",
+  "items": {
+    "enum": [
+      "track",
+      "episode"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / market
      Added value: +{
+  "description": "ISO 3166-1 alpha-2 country code — localises item names; lowercase input is uppercased; defaults to the account market",
+  "pattern": "^[A-Za-z]{2}$",
+  "type": "string"
+}
    • 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

A4.3/5.0
Behavior4/5

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

With no annotations provided, the description carries the behavioral burden. It clearly signals a read-only, lightweight polling behavior and scopes the returned data to 'the item and progress only.' This is useful beyond the schema, though it does not describe what happens when nothing is playing or no active device exists.

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

Conciseness4/5

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

The core guidance is concise and front-loaded, clearly separating the lightweight use case from the full-state alternative. However, the trailing 'Also covers: get_now_playing full-state poll — See also: get_now_playing' is redundant and slightly confusing, preventing a perfect score.

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 read-only polling tool with no output schema and no annotations, the description gives enough context to select and call it: it states what is returned, what is excluded, and points to the sibling for fuller state. It could be more complete by describing empty/no-playback behavior, but the overall context is adequate.

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 the parameters are already well documented. The description does not add meaningful parameter-level detail, which is acceptable because the schema fully explains market, response_format, and additional_types. This aligns with the baseline score of 3 for high schema coverage.

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 a specific verb and resource: a lightweight poll of what is currently playing, returning only the item and progress. It also explicitly differentiates itself from get_now_playing, which provides full session state, so an agent can disambiguate the two tools immediately.

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?

The description gives explicit selection guidance: use this tool for a lightweight poll of current item/progress, and use get_now_playing instead when full session state such as shuffle, repeat, active device, or volume is needed. This directly names the alternative and the condition for choosing it.

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