Skip to main content
Glama
Sign In
Apple Music MCP

Apple Music MCP

by bwu109-netizen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

play_playlist

Start a named playlist in the macOS Music app, optionally enabling shuffle before playback, to control what plays without manual navigation.

Instructions

Start playing a playlist by name, optionally setting shuffle first.

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>"
    },
    "name": "play_playlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
shuffleNo
playlistYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose one ordering trait ('setting shuffle first'), but says nothing about what happens to the current playback/queue, whether the change is reversible, error behavior on an unknown playlist, or whether playback is local or remote.

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 sentence with no filler, front-loading the primary action and appending the optional modifier. Every clause earns its place.

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 two-parameter tool with no output schema, the essentials are present, but with zero annotation coverage and zero schema descriptions the description should say more about side effects on existing playback and failure modes. It is minimally adequate rather than complete.

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 0%, so the description must compensate, and it partially does: 'by name' clarifies how the required playlist parameter is matched, and 'optionally setting shuffle first' conveys that shuffle is a pre-playback toggle. It still omits the expected name format (exact vs fuzzy) and the meaning of the null default.

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?

States a specific verb and resource ('Start playing a playlist by name'), which is clearly distinguishable from siblings like play_track or list_playlists on inspection. However, it never names an alternative tool, so the agent must infer the boundary itself.

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?

There is no guidance on when to choose this over search_and_play, play_track, or playback, nor any prerequisite such as needing an exact playlist name. The 'by name' phrasing hints at an identifier requirement but stops short of stating what happens if the name is ambiguous or absent.

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