Skip to main content
Glama
Sign In
Apple Music MCP

Apple Music MCP

by bwu109-netizen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

play_track

Start playback of a specific song in the macOS Music app using its track ID. Get that ID from search_library or get_playlist_tracks results.

Instructions

Play a specific track by its id (from search_library or get_playlist_tracks).

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": {
      "track_id": "<track_id>"
    },
    "name": "play_track"
  }
}

Input Schema

NameRequiredDescriptionDefault
track_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden but only says 'Play a specific track'. It doesn't disclose whether playback is immediate, requires authentication, or what happens on invalid track IDs.

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 single sentence is concise and front-loaded with the core action and required input. No unnecessary detail, though the parenthetical source hint could be seen as slightly cluttered.

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?

For a simple one-parameter tool with no annotations or output schema, the description provides basic purpose but leaves out key behavioral details like auth requirements, playback behavior, or error handling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% with one parameter. The description clarifies the track_id source ('from search_library or get_playlist_tracks'), which adds some value, but it doesn't describe the parameter's expected format or constraints.

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 (Play) and resource (a specific track), clearly distinguishing it from siblings like play_playlist or search_and_play. It doesn't fully differentiate from search_and_play, but the 'by its id' framing implies a direct play versus a search-based one.

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?

It implies the track id should come from search_library or get_playlist_tracks, giving some retrieval context. However, it doesn't state when to use this tool over alternatives like play_playlist or search_and_play.

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