Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

play

Start or resume Spotify playback, optionally targeting specific tracks, albums, artists, or playlists on a chosen device.

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: describe what would change without performing it. Default false — pass true to preview.
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. Changed2 schema fields changedv3.0.1
    • addedInput schema / properties / dry_run / default
      Added value: +false
    • changedInput schema / properties / dry_run / description
      Previous value: -"Preview only: validate inputs and describe exactly what would change without performing it"New value: +"Preview only: describe what would change without performing it. Default false — pass true to preview."
  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. 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
  4. First observedv1.0.1

TDQS

C2.9/5.0
Behavior2/5

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

Annotations only declare destructiveHint=false. The description adds no detail about authentication needs, how existing playback or queue is affected, device state requirements, or error conditions, so it contributes little beyond the annotation.

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?

Two short sentences, front-loaded and free of wasted words. The second sentence is generic but not redundant, so the structure is efficient.

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?

For an 8-parameter playback control tool surrounded by many siblings, the description is extremely thin. It omits when to use it, device handling, playback behavior, and interaction with other controls; the schema covers parameters but the description does not supply necessary context.

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 all eight parameters are fully documented in the schema. The description only vaguely refers to 'specific content' and adds no syntax or format details beyond what the schema already provides, making the baseline 3 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?

States a specific verb ('start or resume') and resource ('playback'), so the basic action is clear. However, it does not differentiate from siblings like play_from_search or transfer_playback, leaving sibling selection to inference.

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 only guidance is 'Optionally target specific content,' which is vague. There is no indication of when to use this tool versus play_from_search, pause, skip_next, or other playback controls, and no conditions or exclusions are given.

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