Skip to main content
Glama
Sign In
mcp-applemusic

mcp-applemusic

by suleyman416
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

itunes_move_playlist_track

Move a track within an Apple Music playlist by specifying its current position and the target position. Reorder playlist tracks by providing the playlist name and the 1-indexed from and to positions.

Instructions

Move a track inside a playlist from one position (1-indexed) to another position.

Args: playlist: The name of the playlist to edit. from_index: The current 1-indexed position of the track to move. to_index: The target 1-indexed position to move the track to.

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": "<playlist>",
      "from_index": "<from_index>",
      "to_index": "<to_index>"
    },
    "name": "itunes_move_playlist_track"
  }
}

Input Schema

NameRequiredDescriptionDefault
playlistYes
to_indexYes
from_indexYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.5

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description must convey behavior. It states the operation (move) and indexing, but does not disclose potential side effects (e.g., shifting of other tracks, error behavior for invalid indices). For a simple reorder, this is adequate, but it lacks explicit safety or error information.

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 extremely concise: one main sentence and three parameter lines. It is front-loaded with the core action and provides necessary detail without waste. Every sentence earns its place.

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?

The tool is simple (move operation, 3 params, no output schema). The description covers the fundamental action and parameter meanings. It does not mention error cases or reordering semantics, but for an experienced agent, this is sufficient. Given the simplicity, completeness is high.

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 0%, so the description must document parameters. It does so: playlist, from_index, to_index, each with a clear explanation (e.g., 'current 1-indexed position', 'target 1-indexed position'). This adds meaning beyond the schema's bare titles, though it does not cover boundary conditions or valid ranges.

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 action: 'Move a track inside a playlist from one position to another'. It specifies the resource (playlist) and distinguishes this from sibling tools like sorting or removing tracks. The 1-indexed detail adds precision.

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. Related tools like itunes_sort_playlist or itunes_remove_from_playlist exist, but no comparisons or exclusions are mentioned. Usage context is only implied by the function name.

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