Skip to main content
Glama

apple_music

Control Apple Music playback, playlists, and search. Perform actions like play, pause, skip, shuffle, set volume, and more.

Instructions

Control Apple Music. Actions: play, pause, stop, next, prev, restart, now_playing, shuffle_on, shuffle_off, repeat_off, repeat_one, repeat_all, play_playlist, list_playlists, set_volume, love, dislike, search, play_song, queue_next, add_to_playlist, remove_from_playlist, create_playlist, delete_playlist, get_lyrics, radio.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoPlaylist name
levelNoVolume level 0-100
queryNoSearch query (song or artist name)
actionYesplay: Start playback; pause: Pause playback; stop: Stop playback; next: Skip to next track; prev: Go to previous track; restart: Restart current track from the beginning; now_playing: Get info about the currently playing track; shuffle_on: Enable shuffle mode; shuffle_off: Disable shuffle mode; repeat_off: Disable repeat; repeat_one: Repeat current track; repeat_all: Repeat all tracks; play_playlist: Play a specific playlist by name; list_playlists: List all playlists; set_volume: Set Music app volume (independent of system volume); love: Mark the current track as loved; dislike: Mark the current track as disliked; search: Search Music library by song or artist name (returns up to 20 results); play_song: Play a specific song by name; queue_next: Add a song to play next. Note: Music has limited queue support via AppleScript, so this will start playing the track immediately.; add_to_playlist: Add the currently playing track to a playlist; remove_from_playlist: Remove a track from a playlist by name; create_playlist: Create a new empty playlist; delete_playlist: Delete a playlist by name; get_lyrics: Get lyrics of the currently playing track (if available); radio: Open Apple Music radio. Note: AppleScript has limited support for radio stations; this activates the Music app.
confirmNoSet to true to confirm a protected/destructive action. Without this, protected actions return a preview instead of executing.
track_nameNoTrack name to remove
playlist_nameNoTarget playlist name
Behavior2/5

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

The description provides no behavioral details beyond listing action names. It omits critical caveats such as the confirm parameter for protected/destructive actions, the AppleScript limitations for queue_next and radio, and the fact that set_volume is independent of system volume. With no annotations, the description fails to carry the transparency burden.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single long sentence listing 25 actions. While 'Control Apple Music' is front-loaded, the list is bulky and largely duplicates the schema's action enum values without grouping or summarizing, making it less concise and structured than it could be.

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 tool with 25 actions and no output schema, the description is inadequate. It lacks a high-level overview of behavior, fails to mention the confirm mechanism for destructive actions, and does not describe what the tool returns or any cross-cutting limitations. The schema covers individual actions, but the description does not provide enough context for an agent to safely and correctly invoke the tool.

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 coverage for parameters is 100%, so the baseline is 3. The description adds no extra parameter semantics; it merely lists actions without explaining required parameters like 'name', 'level', 'query', or 'confirm'.

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 'Control Apple Music' and enumerates all actions, making the resource and scope clear. However, the verb 'control' is vague and no explicit differentiation from sibling music tools like apple_spotify is provided beyond the app name.

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?

No guidance is given about when to use this tool versus alternatives. There are no mentions of exclusions, prerequisites, or context for choosing Apple Music over other music control tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lacausecrypto/apple-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server