Skip to main content
Glama

itunes_previous

Return to the previous track in Apple Music playback on macOS. Use this tool to navigate backward in your listening queue or playlist.

Instructions

Return to the previous track.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for the 'itunes_previous' tool. It executes an AppleScript command via the run_applescript helper to go to the previous track in the Music (iTunes) application.
    @mcp.tool()
    def itunes_previous() -> str:
        """Return to the previous track."""
        script = 'tell application "Music" to previous track'
        return run_applescript(script)
  • Helper function used by itunes_previous (and other tools) to run AppleScript commands using 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?

No annotations are provided, so the description carries full burden. It states the action ('Return to the previous track') but lacks behavioral details: it doesn't specify what happens if no previous track exists, whether playback automatically resumes, if it affects playlists or queues, or any error conditions. 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 no wasted words. It's front-loaded with the core action, making it immediately clear. Every word earns its place by conveying the essential purpose without redundancy.

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's complexity (simple navigation with 0 parameters) and the presence of an output schema (which handles return values), the description is minimally adequate. However, as a mutation tool with no annotations, it should provide more behavioral context (e.g., what happens on error or edge cases) to be fully complete.

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 with 100% schema description coverage, so the schema fully documents the absence of inputs. The description doesn't need to add parameter information, and it correctly doesn't mention any parameters, aligning with the schema. Baseline 4 is appropriate for zero-parameter tools.

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 ('Return to') and target resource ('the previous track'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'itunes_next' or 'itunes_play_song', but the verb 'return to' implies navigation rather than playback initiation.

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 about when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., requires iTunes to be playing), exclusions, or relationships with sibling tools like 'itunes_next' for forward navigation or 'itunes_play' for resuming playback.

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