Skip to main content
Glama
Sign In
Spotify MCP Server

Spotify MCP Server

by MadhurToshniwal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

toggle_shuffle

Control shuffle mode for Spotify playback. Enable or disable random track order to customize your listening experience.

Instructions

Turn shuffle on or off

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": {
      "state": "<state>"
    },
    "name": "toggle_shuffle"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateYesTrue to enable shuffle, false to disable

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, the description carries full burden but only states the basic action without behavioral details. It doesn't disclose if this affects current playback, requires specific permissions, has side effects (e.g., changing queue order), or provides feedback on success/failure, which is inadequate for a mutation tool.

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 a single, efficient sentence with zero wasted words. It's front-loaded with the core action and states exactly what the tool does, making it highly scannable and appropriate for a simple toggle function.

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 incomplete. It lacks context about effects on playback, error conditions, or return values, leaving significant gaps in understanding how to use it effectively in practice.

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 fully documents the single parameter 'state'. The description adds no additional meaning beyond implying a boolean toggle, matching the schema's 'True to enable, false to disable'. This meets the baseline for high schema coverage.

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 clearly states the action ('Turn') and resource ('shuffle') with specific states ('on or off'), making the purpose immediately understandable. It doesn't distinguish from sibling tools like 'play_track' or 'pause_playback', but the verb+resource combination is unambiguous for its domain.

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 about when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., requires active playback), exclusions, or related tools like 'play_track' that might affect shuffle behavior, leaving usage context implied at best.

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