Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

play

Start or resume Spotify playback on any device. Target specific tracks, albums, playlists, or artists, and choose the starting position.

Instructions

Start or resume playback. Optionally target specific content.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urisNoUp to 100 track/episode URIs to play as an ad-hoc queue
offsetNoIndex within an album/playlist context to start from. Ignored for ad-hoc uris; not valid for artist contexts (use offset_uri instead).
dry_runNoPreview only: validate inputs and describe exactly what would change without performing it
device_idNoTarget device ID; uses active device if omitted
offset_uriNoTrack URI inside the context to start from — required for artist contexts, where a numeric index is rejected
context_uriNoSpotify URI for an album, artist, or playlist
position_msNoSeek position to start at (ms)
response_formatNo'concise' = human prose, 'detailed' = more fields in prose, 'json' = raw API objectconcise

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv1.26.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / dry_run
      Added value: +{
+  "description": "Preview only: validate inputs and describe exactly what would change without performing it",
+  "type": "boolean"
+}
    • changedInput schema / properties / offset / description
      Previous value: -"Index within context to start from"New value: +"Index within an album/playlist context to start from. Ignored for ad-hoc uris; not valid for artist contexts (use offset_uri instead)."
    • addedInput schema / properties / offset / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / offset_uri
      Added value: +{
+  "description": "Track URI inside the context to start from — required for artist contexts, where a numeric index is rejected",
+  "type": "string"
+}
    • addedInput schema / properties / position_ms / maximum
      Added value: +9007199254740991
    • 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"
+}
    • addedInput schema / properties / uris / maxItems
      Added value: +100
  2. First observedv1.0.1

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full behavioral disclosure burden. It only says 'Start or resume playback' without disclosing side effects such as changing current playback state, requiring a target device, or that dry_run can preview changes. The schema reveals behavior (e.g., dry_run, context_uri, offset_uri), but the description itself adds no transparency beyond the raw action.

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 description is two short sentences with no filler words. It names the core action first and adds a scope hint second. It is not embarassingly short enough to be under-specified for purpose, but it could perhaps integrate the targeting hint better. Overall it is efficient and well-structured.

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

Completeness2/5

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

Given the tool has 8 optional parameters, no output schema, and no annotations, the description is too thin to support correct invocation in all contexts. It does not explain how start/resume behaves differently across contexts (album vs artist vs ad-hoc queue), when offset_uri is required, or what happens when no device is specified. An agent would need to rely on schema alone and could still miss important behavioral constraints.

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 covers 100% of parameters with meaningful descriptions, so the baseline is 3 and the description does not need to repeat parameter details. The phrase 'Optionally target specific content' hints at context_uri/uris but adds no new meaning. Since the description does not conflict with or expand on the schema, a 3 is appropriate.

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?

The description states a clear verb ('Start or resume playback') and resource (playback), which is specific and not a tautology. It also hints at targeting content ('Optionally target specific content'). However, it does not distinguish itself from sibling tools like play_on, play_at, or queue_next, which all involve starting or resuming playback in some way.

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 is given about when to use this tool versus the many sibling playback tools such as play_on, play_at, queue_next, or resume_playback_position. The description implies it is the general entry point for starting/resuming playback, but lacks any exclusions, prerequisites (e.g., active device), or alternative tool mentions.

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