Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_currently_playing

Read-onlyIdempotent

Poll what is playing right now—track or episode and progress—without full session details; use get_now_playing for shuffle, repeat, device, or 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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
marketNoISO 3166-1 alpha-2 country code — localises item names; lowercase input is uppercased; defaults to SPOTIFY_MCP_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. Changed1 schema field changedv2.1.2
    • changedInput schema / properties / market / description
      Previous value: -"ISO 3166-1 alpha-2 country code — localises item names; lowercase input is uppercased; defaults to the account market"New value: +"ISO 3166-1 alpha-2 country code — localises item names; lowercase input is uppercased; defaults to SPOTIFY_MCP_MARKET"
  2. Changed2 schema fields changedv1.31.0
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
  3. 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"
+}
  4. First observedv1.0.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds real value beyond that by disclosing the scope of the response payload (item and progress only), letting the agent anticipate a lighter result set than the sibling. It does not mention auth or rate limits, but neither is critical for a poll.

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?

Two tightly packed sentences with zero filler; the payload scope is front-loaded immediately followed by the routing instruction. Every clause earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only poll with no output schema, the description covers what is needed: purpose, payload scope, and the sibling alternative. Nothing an agent requires in order to choose and call this tool is missing.

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% – market, response_format, and additional_types are each fully documented in the schema, including defaults and enum meanings. The description adds no parameter guidance, so the baseline of 3 applies.

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 action (poll what is playing right now) and scopes it precisely with 'lightweight' and 'the item and progress only', which distinguishes it from the richer get_now_playing sibling named in the same sentence.

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?

Explicitly names the alternative tool (get_now_playing) and states the condition that selects it ('For full session state ... use get_now_playing instead'). This is textbook when-to-use/when-not-to-use routing.

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