Skip to main content
Glama
Sign In
Apple Music MCP

Apple Music MCP

by bwu109-netizen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_playlist_tracks

Retrieve the tracks inside an Apple Music playlist by exact name, returning up to a set limit of songs for review or further processing.

Instructions

List tracks in a playlist (by exact name).

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": "get_playlist_tracks"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
playlistYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/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 behavioral burden but says nothing about whether this is a read-only listing, whether it paginates (the limit param defaults to 100), or what happens when the exact name is not found. 'List' implies a read, but nothing confirms it.

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?

A single short sentence with the resource front-loaded and the matching constraint appended. No waste, though it is terse to the point of under-specification rather than genuine conciseness.

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?

No output schema, no annotations, and 0% schema coverage, so the description should be doing more work. It omits the return shape (track fields, ordering), pagination behavior, and the failure mode for a non-matching name.

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% for both parameters. The description clarifies the 'playlist' argument must match an exact name, which adds real value, but the 'limit' parameter (default 100) is completely unaddressed in both schema and description.

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 ('List tracks in a playlist') that is clearly distinct from sibling list_* tools like list_playlists. The parenthetical narrows the lookup semantics, but no sibling is named to sharpen the boundary against list_playlists or play_playlist.

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 '(by exact name)' note is the only usage signal, and it constrains matching rather than telling the agent when to pick this tool over list_playlists, play_playlist, or compare_playlists. No prerequisites, no when-not-to-use guidance.

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