Skip to main content
Glama
Sign In
Apple Music MCP

Apple Music MCP

by bwu109-netizen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

search_and_play

Search your Apple Music library by query and immediately play the matching item, returning other candidates for selection.

Instructions

Search the library and immediately play the best match. Also returns other candidates.

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": {
      "query": "<query>"
    },
    "name": "search_and_play"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoall
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations provided, the description carries the full disclosure burden, and it does surface one important side effect: the tool immediately starts playback and also returns other candidates. However, it says nothing about what happens to currently playing audio, how a 'best match' is chosen, or what happens when no match exists.

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?

Two short, front-loaded sentences with zero padding: the action is stated first and the secondary return behavior second. Nothing is wasted.

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 output schema, the description partially covers returns ('also returns other candidates'), but it omits the kind filter semantics and the effect on existing playback state. For a tool that both reads and mutates playback, that is a meaningful gap.

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 two parameters, so the description must compensate, and it does not. The 'kind' enum (all/songs/artists/albums) is never mentioned, and 'query' is only obliquely implied by 'Search the library', leaving the filter parameter undocumented anywhere.

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 names a specific compound verb (search + play) and resource (library), and the phrase 'immediately play the best match' distinguishes it from the sibling search_library, which presumably only searches. It stops short of naming the alternatives explicitly, so it is clear but not fully differentiated.

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 statement of when to use this combined tool versus search_library plus play_track, and no prerequisites or exclusions are given. The combined search-and-play intent is only implied by the sentence structure.

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