Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

transfer_playback

Move Spotify playback to another Connect device by id, label, or name substring. Preserve track position, shuffle, and repeat modes when switching devices.

Instructions

Move playback to a different Spotify Connect device, named by exact id, by the label you gave it, or by a case-insensitive name substring. A plain transfer restarts the track at 0:00 on the target; preserve_position: true carries the current track and play position across instead, and restore_shuffle_repeat: true re-applies the current shuffle and repeat modes on the target. Quota: 1 read to resolve the device, then 1–4 writes depending on the flags.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
playNoForce play (true) or arrive paused (false); omit to preserve the current play state. With preserve_position, true also resumes a session that is currently paused.
deviceYesTarget device: exact id, sidecar label, or case-insensitive name substring
volumeNoVolume to set on the target after transfer, 0–100
dry_runNoPreview only: describe what would change without performing it. Default false — pass true to preview.
device_idNoDEPRECATED: use `device`
response_formatNo'concise' = human prose, 'detailed' = more fields in prose, 'json' = raw API objectconcise
preserve_positionNoResume the current track at its current position on the target instead of restarting it (default: false)
restore_shuffle_repeatNoRe-apply the current shuffle and repeat modes on the target (default: false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv3.0.1
    • addedInput schema / properties / device
      Added value: +{
+  "description": "Target device: exact id, sidecar label, or case-insensitive name substring",
+  "minLength": 1,
+  "type": "string"
+}
    • changedInput schema / properties / device_id / description
      Previous value: -"Target device ID to transfer playback to"New value: +"DEPRECATED: use `device`"
    • 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."
    • changedInput schema / properties / play / description
      Previous value: -"Force play immediately (default: maintain current state)"New value: +"Force play (true) or arrive paused (false); omit to preserve the current play state. With preserve_position, true also resumes a session that is currently paused."
    • addedInput schema / properties / preserve_position
      Added value: +{
+  "description": "Resume the current track at its current position on the target instead of restarting it (default: false)",
+  "type": "boolean"
+}
    • addedInput schema / properties / restore_shuffle_repeat
      Added value: +{
+  "description": "Re-apply the current shuffle and repeat modes on the target (default: false)",
+  "type": "boolean"
+}
    • addedInput schema / properties / volume
      Added value: +{
+  "description": "Volume to set on the target after transfer, 0–100",
+  "maximum": 100,
+  "minimum": 0,
+  "type": "integer"
+}
    • changedInput schema / required
      Previous value: -[
-  "device_id"
-]New value: +[
+  "device"
+]
  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
    • 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"
+}
    • 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.4/5.0
Behavior5/5

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

Annotations only declare destructiveHint=false, so the description carries real weight and delivers: it discloses that a plain transfer restarts the track at 0:00, that preserve_position carries position across, that shuffle/repeat can be re-applied, and gives an explicit write-quota cost (1 read + 1–4 writes). This is exactly the behavior an agent needs before invoking a state-changing playback operation.

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?

Three dense sentences, front-loaded with the core action and then the flag semantics and cost. Every clause carries information an agent would otherwise have to guess; no filler or restatement of the name.

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 an 8-parameter mutation tool with no output schema, the description covers the risky aspects: track position, shuffle/repeat restoration, and operation cost. It omits any mention of dry_run previewing or the deprecated device_id alias, both of which an agent might want surfaced at the description level.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3, but the description adds genuine value by describing the interplay between flags (e.g. preserve_position combined with play resumes a paused session) and by spelling out the three device-resolution modes. It does not, however, cover volume, dry_run, or the deprecated device_id, leaving those to the schema.

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 verb and resource ('Move playback to a different Spotify Connect device') and immediately scopes how the target is identified. It is clearly distinguishable from siblings like play, pause, seek, and set_volume, which operate on the current session rather than relocating it.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains the behavioral variants (plain transfer vs preserve_position vs restore_shuffle_repeat), which implies when each flag is appropriate, but it never explicitly names an alternative tool or a when-not condition. An agent must infer the choice of flags rather than being routed 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