Skip to main content
Glama
Sign In
Spotify MCP Server

Spotify MCP Server

by MadhurToshniwal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

set_volume

Adjust Spotify playback volume to a specific level between 0 and 100 using voice commands or conversational AI.

Instructions

Set playback volume

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": {
      "volume": "<volume>"
    },
    "name": "set_volume"
  }
}

Input Schema

NameRequiredDescriptionDefault
volumeYesVolume level (0-100)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the action without disclosing behavioral traits. It doesn't mention effects (e.g., immediate volume change, persistence), permissions needed, rate limits, or error conditions, which are critical for a mutation tool like this.

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 extremely concise at three words, front-loading the core action without any wasted text. Every word earns its place by directly conveying the tool's function, making it efficient and easy to parse.

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?

Given this is a mutation tool with no annotations and no output schema, the description is incomplete. It lacks information on what happens after setting volume (e.g., success confirmation, error handling), behavioral context, or integration with sibling tools, leaving significant gaps for agent understanding.

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?

The input schema has 100% description coverage, detailing the 'volume' parameter with range and type. The description adds no additional meaning beyond the schema, such as units interpretation or default behavior, so it meets the baseline of 3 where schema does the heavy lifting.

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 'Set playback volume' clearly states the action (set) and target resource (playback volume), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'pause_playback' or 'resume_playback' in terms of audio control context, though the specific function is distinct.

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 is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., active playback), exclusions, or related tools like 'play_track' for starting playback before adjusting volume, leaving usage context implied but unspecified.

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