Spotify MCP Server

Overview Schema Source Related Servers Discussions Admin

spotify_reorder_playlist_tracks

Move tracks within a Spotify playlist to change their order. Specify the start position, number of tracks, and where to insert them.

Instructions

Reorder tracks in a playlist

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": {
      "playlist_id": "<playlist_id>",
      "range_start": "<range_start>",
      "insert_before": "<insert_before>"
    },
    "name": "spotify_reorder_playlist_tracks"
  }
}

Input Schema

Name	Required	Description
`playlist_id`	Yes	Spotify playlist ID
`range_start`	Yes	Position of the first track to move
`snapshot_id`	No	Playlist snapshot ID for concurrent modification safety
`range_length`	No	Number of tracks to move (default: 1)
`insert_before`	Yes	Position where tracks should be inserted

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.4Sep 27, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description must carry the full behavioral burden. It does not disclose that this is a mutation that changes playlist order, requires playlist modification permissions, or uses snapshot_id for concurrency safety. Only the core action is stated.

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 a single, front-loaded sentence with no wasted words. It is concise and easy to parse, though very minimal. It earns its place without redundancy.

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 five parameters, no annotations, no output schema, and a mutation operation, the description is incomplete. It does not explain side effects, required auth, or how the reorder interacts with snapshot_id. The schema helps with parameters, but behavior and usage context are largely missing.

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 already documents all five parameters thoroughly. The description adds no additional parameter meaning or usage notes. When the schema does the heavy lifting, a baseline of 3 is appropriate.

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: 'Reorder tracks in a playlist.' This clearly identifies the tool's action. However, it does not explicitly distinguish it from sibling playlist-mutation tools like add, remove, or update, so it stops short of a 5.

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 on when to use this tool versus alternatives. It simply states what it does, leaving the agent to infer appropriate contexts from the name alone. No prerequisites, exclusions, or alternative tools are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.