Apple Music MCP

Overview Schema Source Related Servers Discussions Admin

compare_playlists

Find tracks in one Apple Music playlist that are not in other playlists. Identify unique songs to clean up, merge, or edit collections.

Instructions

Tracks in playlist that are NOT in any of the against playlists (read-only).

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

Input Schema

Name	Required	Description	Default
`limit`	No
`against`	Yes
`playlist`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 4, 2026

TDQS

B3.3/5.0

Behavior3/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 '(read-only)', which is a useful safety signal beyond the bare schema, but says nothing about pagination behavior driven by `limit`, result ordering, or the size/shape of the returned set.

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 front-loaded sentence with no wasted words; the core semantics appear immediately and the read-only marker is efficiently parenthesized.

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?

With no annotations, no output schema, and 0% parameter description coverage, the description covers the essential comparison semantics but leaves gaps around the `limit` parameter, return shape, and result ordering that an agent calling this tool would benefit from knowing.

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. It meaningfully clarifies the two required parameters by tying `playlist` and `against` to the set-difference semantics, but the `limit` parameter (default 200) is never mentioned, leaving one of three params undocumented in both schema and prose.

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 gives a specific operation and precise semantics: it returns tracks in `playlist` that are NOT in any of the `against` playlists, which is a set-difference. An agent can distinguish this from sibling tools like get_playlist_tracks or compare-style operations. It stops short of naming a sibling it displaces, so it lands at 4 rather than 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?

There is no explicit when-to-use guidance, no when-not-to-use, and no mention of alternatives such as get_playlist_tracks. The purpose is implied by the semantics but the agent is left to infer when comparison is the right choice.

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

Deploy Server