Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

set_repeat

Set Spotify repeat mode to off, context, or track. Use optional device ID and dry-run to validate changes before applying.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stateYesRepeat mode
dry_runNoPreview only: validate inputs and describe exactly what would change without performing it
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. 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"
+}
  2. 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"
+}
  3. First observedv1.0.1

TDQS

A3.7/5.0
Behavior2/5

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It only says what the tool sets, not whether an active playback device is required, whether device_id defaults to the active device, what side effects occur, or whether the operation is reversible. This is a thin disclosure 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?

A single, front-loaded sentence that states the action and the meaningful option semantics without filler. Every word contributes to understanding the tool.

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 simple playback setter, the schema plus description cover the required state parameter and the core enum semantics. Missing pieces are behavioral expectations, device handling, and any distinction from repeat_queue_toggle, which leaves the description adequate but incomplete.

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 schema already documents all parameters, but the description adds meaning beyond the schema by explaining the state enum: 'context' means repeat playlist/album and 'track' means repeat single track. This is genuinely useful semantic enrichment.

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?

States a specific verb and resource: 'Set repeat mode' with the exact allowed values (off, context, track). The parentheticals clarify the meaning of context and track, making the tool's purpose unambiguous and distinct from sibling playback controls.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when the tool should be used: whenever the caller wants to change the playback repeat mode. However, it provides no explicit when-not-to-use guidance or comparison to the closely named sibling repeat_queue_toggle, so an agent must infer the difference rather than being told.

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