Skip to main content
Glama
Sign In
Spotify MCP Server

Spotify MCP Server

by llyfn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

set_repeat

Set the repeat mode for Spotify playback to repeat track, context, or turn it off. Optionally specify a device ID.

Instructions

Set the repeat mode for playback.

    Args:
        state: Repeat mode: "track", "context", or "off".
        device_id: ID of the device. If not provided, uses the active device.

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": "set_repeat"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateYes
device_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.7/5.0
Behavior3/5

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

Without annotations, the description carries the burden. It mentions that device_id defaults to the active device, which is useful, but does not disclose other behavioral traits like authentication needs or side effects of changing repeat mode during playback.

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?

The description is short and front-loaded with the purpose, followed by parameter details. It is concise with no wasted words, though a more structured format (e.g., bullet points) could improve readability.

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

Completeness4/5

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

For a simple setter tool, the description covers the essential parameter behavior. The output schema presumably documents return values, so the description is fairly complete, though it lacks details on the meaning of each repeat mode.

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?

The description adds meaning beyond the schema by listing the allowed values for state (track, context, off) and explaining that device_id defaults to the active device. Since schema description coverage is 0%, this is valuable, though it could further explain what each mode does.

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 tool sets the repeat mode for playback, with a specific verb and resource. It distinguishes from sibling tools like toggle_shuffle or set_volume by focusing solely on repeat.

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, such as using toggle_shuffle for shuffle or other playback controls. No context about prerequisites like having an active device is mentioned.

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