Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

set_repeat

Control Spotify repeat mode by selecting off, context to repeat a playlist or album, or track to repeat one song. Target a device or preview changes with dry_run.

Instructions

Set repeat mode: off, context (repeat playlist/album), or track (repeat single track)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stateYesRepeat mode
dry_runNoPreview only: describe what would change without performing it. Default false — pass true to preview.
device_idNoTarget device ID
response_formatNo'concise' = human prose, 'detailed' = more fields in prose, 'json' = raw API objectconcise

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv3.0.1
    • 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."
  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

B3.3/5.0
Behavior2/5

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

The only annotation is destructiveHint=false, so the description carries most of the behavioral burden. It does not disclose whether the change is immediate, whether it requires an active playback context, what happens on invalid devices, or what dry_run does. It lists the mode values but adds little behavioral context beyond the schema.

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 front-loaded sentence that states the operation and immediately enumerates its values. Every word earns its place, and there is no filler or redundancy.

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?

This is a simple state-setting tool with a fully described schema and no output schema. The description adequately conveys the operation and the meaning of the required enum values. It does not cover when to use it or the purpose of optional parameters like dry_run, but those gaps are minor for such a low-complexity tool.

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. The description adds meaningful semantics for the state enum by explaining that 'context' repeats a playlist/album and 'track' repeats a single track, which goes beyond the schema's terse 'Repeat mode' label. The other parameters are left to the schema, which is acceptable given full 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 states a specific verb and resource: 'Set repeat mode.' It also lists the three possible modes, making the operation unambiguous. However, it does not explicitly distinguish this tool from the sibling set_shuffle, which controls a related but different playback setting.

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?

The description offers no guidance about when to use this tool versus alternatives. It does not mention set_shuffle or any other sibling, nor does it state prerequisites such as an active playback session or device targeting. The agent must infer usage entirely from the tool name and schema.

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