Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

set_volume

Adjust Spotify playback volume on one, several, or all live devices: set or nudge levels, mute or unmute, apply presets, or copy the active device's level.

Instructions

Set playback volume on one device, on a selection of devices, or across every live device. volume_percent sets an absolute level; delta_step nudges the current level by a signed step. op picks the variant: "mute" drops to 0 and remembers the level, "unmute" restores what mute remembered, "preset" applies the per-device presets stored by set_device_volume_preset, and "level" with no volume_percent copies the active device's level to the others. Quota: 1 write for a single device; 1 read + N writes when fanning out.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
opNoVariant: "level" (default) set or copy a level, "mute", "unmute", "preset"
dry_runNoPreview only: describe what would change without performing it. Default false — pass true to preview.
device_idNoDevice ID for a single-device write (default: the active device)
delta_stepNoSigned nudge, e.g. +10 or -10, clamped to 0–100. Mutually exclusive with volume_percent.
device_idsNoFor op "level" with volume_percent: fan out to these device ids or names. Mutually exclusive with all_devices.
all_devicesNoFor op "level" with volume_percent: set every volume-capable device, not a named selection.
volume_percentNoAbsolute level 0–100. Mutually exclusive with delta_step.
response_formatNo'concise' = human prose, 'detailed' = more fields in prose, 'json' = raw API objectconcise
exclude_device_idNoFor op "level" with no volume_percent: leave this device untouched while levelling the rest

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv3.0.1
    • addedInput schema / properties / all_devices
      Added value: +{
+  "description": "For op \"level\" with volume_percent: set every volume-capable device, not a named selection.",
+  "type": "boolean"
+}
    • addedInput schema / properties / delta_step
      Added value: +{
+  "description": "Signed nudge, e.g. +10 or -10, clamped to 0–100. Mutually exclusive with volume_percent.",
+  "maximum": 100,
+  "minimum": -100,
+  "type": "integer"
+}
    • changedInput schema / properties / device_id / description
      Previous value: -"Target device ID"New value: +"Device ID for a single-device write (default: the active device)"
    • addedInput schema / properties / device_ids
      Added value: +{
+  "description": "For op \"level\" with volume_percent: fan out to these device ids or names. Mutually exclusive with all_devices.",
+  "items": {
+    "minLength": 1,
+    "type": "string"
+  },
+  "type": "array"
+}
    • 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."
    • addedInput schema / properties / exclude_device_id
      Added value: +{
+  "description": "For op \"level\" with no volume_percent: leave this device untouched while levelling the rest",
+  "type": "string"
+}
    • addedInput schema / properties / op
      Added value: +{
+  "description": "Variant: \"level\" (default) set or copy a level, \"mute\", \"unmute\", \"preset\"",
+  "enum": [
+    "level",
+    "mute",
+    "unmute",
+    "preset"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / volume_percent / description
      Previous value: -"Volume level 0–100"New value: +"Absolute level 0–100. Mutually exclusive with delta_step."
    • removedInput schema / required
      Removed value: -[
-  "volume_percent"
-]
  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

A4.7/5.0
Behavior5/5

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

With only destructiveHint=false in annotations, the description carries the behavioral load well: it discloses that mute remembers the prior level and unmute restores it, that level with no volume_percent copies the active device's level to others, and it states the quota cost (1 write single; 1 read + N writes fanning out). That is substantive context the annotations do not provide.

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?

Every sentence earns its place: the target scope is front-loaded, then the two level-setting modes, then op variants, then quota. No repetition of what the schema already states verbatim, and it is compact despite covering nine parameters.

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

Completeness5/5

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

For a nine-parameter, no-output-schema mutation tool with thin annotations, the description covers target scope, the mode selection (absolute vs delta), each op's semantics, dry_run preview, and quota cost. Nothing an agent needs to invoke it correctly is missing.

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 real meaning beyond the schema by explaining op interactions (what 'preset' and 'level' actually do) and how volume_percent, delta_step, device_ids, all_devices and exclude_device_id combine. This is more than the schema conveys on its own.

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 (set) and resource (playback volume) and immediately scopes the target space: one device, a selection, or every live device. It also names the related sibling set_device_volume_preset, so an agent can distinguish preset-applying from preset-storing without opening another schema.

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

Usage Guidelines4/5

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

Gives explicit when-to-use guidance per op variant (mute/unmute/preset/level) and clarifies the volume_percent vs delta_step choice. It references set_device_volume_preset as the tool that stores presets, implying the alternative, but stops short of an explicit 'use X instead when Y' rule.

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