Skip to main content
Glama

stop_playback

Stop playback in Ableton Live sessions to pause music production or testing. This tool halts the current session playback through the AbletonMCP server.

Instructions

Stop playing the Ableton session.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The MCP tool handler for 'stop_playback'. Connects to Ableton remote script via get_ableton_connection() and sends the 'stop_playback' command, returning success or error message.
    @mcp.tool()
    def stop_playback(ctx: Context) -> str:
        """Stop playing the Ableton session."""
        try:
            ableton = get_ableton_connection()
            result = ableton.send_command("stop_playback")
            return "Stopped playback"
        except Exception as e:
            logger.error(f"Error stopping playback: {str(e)}")
            return f"Error stopping playback: {str(e)}"
  • The actual implementation in the Ableton Remote Script. Called by the MCP server when 'stop_playback' command is forwarded. Invokes self._song.stop_playing() to stop Ableton playback.
    def _stop_playback(self):
        """Stop playing the session"""
        try:
            self._song.stop_playing()
            
            result = {
                "playing": self._song.is_playing
            }
            return result
        except Exception as e:
            self.log_message("Error stopping playback: " + str(e))
            raise
  • The send_command method recognizes 'stop_playback' as a state-modifying command, adding delays before/after execution for reliable communication with Ableton.
    is_modifying_command = command_type in [
        "create_midi_track", "create_audio_track", "set_track_name",
        "create_clip", "add_notes_to_clip", "set_clip_name",
        "set_tempo", "fire_clip", "stop_clip", "set_device_parameter",
        "start_playback", "stop_playback", "load_instrument_or_effect"
    ]
  • Dispatch logic in the remote script's _process_command method that routes the 'stop_playback' command to the _stop_playback handler.
    elif command_type == "stop_playback":
        result = self._stop_playback()
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('stop playing') but doesn't mention side effects (e.g., whether it resets playback position, affects other session components, or requires specific permissions). For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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, clear sentence with zero wasted words. It's front-loaded with the core action and resource, making it highly efficient and easy to parse.

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?

Given the tool's mutation nature (stopping playback) and lack of annotations or output schema, the description is incomplete. It doesn't address behavioral nuances, error conditions, or what happens after execution (e.g., does it return a status?). For a tool that likely interacts with live session state, more context is needed.

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 zero parameters, and schema description coverage is 100%, so there's no need for parameter documentation in the description. The description appropriately focuses on the action without unnecessary parameter details, earning a high baseline score for this dimension.

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 ('stop playing') and the target resource ('the Ableton session'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from the sibling tool 'stop_clip', which might cause confusion about scope.

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?

The description provides no guidance on when to use this tool versus alternatives like 'stop_clip' or when playback should be stopped. There's no mention of prerequisites, such as requiring playback to be active, or contextual factors for choosing this tool.

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/ahujasid/ableton-mcp'

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