Spotify MCP Server

setVolume

Adjust Spotify playback volume to a specific percentage between 0 and 100. Requires Spotify Premium account and device ID for targeted control.

Instructions

Set the playback volume to a specific percentage (0-100). Requires Spotify Premium.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "volumePercent": "<volumePercent>"
    },
    "name": "setVolume"
  }
}

Input Schema

Name	Required	Description	Default
`volumePercent`	Yes	The volume to set (0-100)
`deviceId`	No	The Spotify device ID to set volume on

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.0.0Jan 2, 2026

TDQS

A3.9/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the Spotify Premium requirement but doesn't describe what happens if no device is specified (deviceId is optional), whether changes are immediate, or what happens on failure. The description provides basic context but lacks operational details.

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?

The description is perfectly concise - a single sentence that communicates the core purpose and key constraint. Every word earns its place with no redundancy or unnecessary elaboration.

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 mutation tool with no annotations and no output schema, the description provides basic purpose and constraints but lacks information about return values, error conditions, or device selection behavior when deviceId is omitted. Given the complexity of volume control across devices, more context would be helpful.

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 fully documents both parameters. The description mentions 'percentage (0-100)' which aligns with the schema's volumePercent documentation but adds no additional semantic context beyond what the structured schema provides.

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?

The description clearly states the action ('Set the playback volume') and the resource ('to a specific percentage'), with precise boundaries (0-100). It distinguishes from sibling 'adjustVolume' by specifying exact percentage setting rather than relative adjustment.

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?

The description explicitly states 'Requires Spotify Premium' which provides important context about prerequisites. However, it doesn't specify when to use this versus the sibling 'adjustVolume' tool for relative volume changes, leaving some ambiguity about tool selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.