Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

transfer_playback

Move active Spotify playback to another Spotify Connect device. Provide the target device ID to redirect audio output.

Instructions

Move playback to a different Spotify Connect device

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
playNoForce play immediately (default: maintain current state)
dry_runNoPreview only: validate inputs and describe exactly what would change without performing it
device_idYesTarget device ID to transfer playback to
response_formatNo'concise' = human prose, 'detailed' = more fields in prose, 'json' = raw API objectconcise

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+}
  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 carries the full burden. 'Move' implies a mutation, but it does not disclose whether current playback state (position, queue) is preserved, whether the target device must already be active, or what happens to the source device. The 'play' parameter hints at state behavior, but the description itself does not explain it.

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?

A single, front-loaded sentence that states the action and target. This is efficient and immediately scannable; no filler exists, though it could add a bit more behavioral context without becoming bloated.

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 a mutation tool with no annotations and no output schema, the description is thin. It lacks details about playback state preservation, error conditions, device availability requirements, and response format. The schema covers parameters, but behavioral and environmental context is missing. Sibling tools like transfer_playback_with_state and switch_device suggest adjacent use cases that this description does not disambiguate.

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 schema already documents all four parameters, including defaults and enums. The description adds no additional parameter-level semantics, but the schema fully carries that weight. Baseline 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 'Move playback to a different Spotify Connect device' uses a clear verb ('Move') and a specific resource ('playback' to a 'Spotify Connect device'). It distinguishes itself functionally from sibling tools like pause, play, and switch_device, though it doesn't explicitly contrast with them.

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 explicit guidance on when to use this tool versus alternatives like switch_device, handoff, or transfer_playback_with_state. The description implies a use case (moving playback) but does not state prerequisites (e.g., device must be active) or exclusions.

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