Skip to main content
Glama

itunes_play

Start playback in Apple Music on macOS to resume listening to your music library or current queue.

Instructions

Start playback in Music (iTunes).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for the 'itunes_play' tool. It is decorated with @mcp.tool() which registers it with the MCP server. The function sends an AppleScript command to play music in the Music (iTunes) app using the run_applescript helper.
    @mcp.tool()
    def itunes_play() -> str:
        """Start playback in Music (iTunes)."""
        script = 'tell application "Music" to play'
        return run_applescript(script)
  • Helper function used by 'itunes_play' and other tools to execute AppleScript via subprocess.
    def run_applescript(script: str) -> str:
        """Execute an AppleScript command via osascript and return its output."""
        result = subprocess.run(["osascript", "-e", script], capture_output=True, text=True)
        if result.returncode != 0:
            return f"Error: {result.stderr.strip()}"
        return result.stdout.strip()
Behavior2/5

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

With no annotations, the description carries full burden but provides minimal behavioral insight. It states the action ('Start playback') but doesn't disclose what happens if playback is already active, whether it requires specific permissions, or what the expected outcome is. This leaves significant gaps for a mutation tool.

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?

The description is a single, efficient sentence with zero wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly.

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?

Given the tool has no parameters and an output schema exists, the description doesn't need to cover those aspects. However, as a mutation tool with no annotations, it should provide more behavioral context (e.g., what 'Start playback' entails, error conditions). The current description is minimal but not fully complete for safe use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, earning a baseline score of 4 for not adding unnecessary information.

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 clearly states the action ('Start playback') and target resource ('Music (iTunes)'), making the purpose immediately understandable. However, it doesn't distinguish this tool from its sibling 'itunes_play_song', which suggests a similar playback function with song-specific parameters.

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 provided on when to use this tool versus alternatives like 'itunes_play_song' or 'itunes_pause'. The description implies it initiates playback, but doesn't specify context (e.g., resuming paused playback vs. starting a new track) or prerequisites.

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/kennethreitz/mcp-applemusic'

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