Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

set_shuffle

Enable or disable shuffle mode for Spotify playback, optionally targeting a specific device and previewing changes.

Instructions

Enable or disable shuffle mode

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stateYestrue = shuffle on, false = shuffle off
dry_runNoPreview only: describe what would change without performing it. Default false — pass true to preview.
device_idNoTarget device ID
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. Changed1 schema field changedv1.28.0
    • addedInput schema / properties / dry_run
      Added value: +{
+  "description": "Preview only: validate inputs and describe exactly what would change without performing it",
+  "type": "boolean"
+}
  4. Changed2 schema fields changedv1.26.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • 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"
+}
  5. 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 supply only destructiveHint=false, so the description carries the full burden of behavioral disclosure and does not meet it. It never says whether the change is session-only or persisted, whether it requires an active playback context, or how device targeting interacts with the setting.

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 short clause with the action front-loaded and zero filler. It is efficient, though the terseness contributes to the informational gaps noted elsewhere.

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

Completeness3/5

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

For a 4-parameter mutation tool with no output schema, the schema and annotations cover parameters and the non-destructive hint, leaving the definition minimally adequate. Missing scope/persistence behavior and sibling differentiation keep it from being complete.

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%, and each parameter (state, dry_run, device_id, response_format) is well documented in the schema itself. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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 pair ('Enable or disable') and resource ('shuffle mode'), so the agent knows exactly what it does. It does not distinguish itself from the sibling 'playlist_shuffle', which is a plausible confusion point given both deal with shuffling.

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 on when to use this versus set_repeat, playlist_shuffle, or a playback-state tool, and no prerequisites stated. The agent must infer context entirely.

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