Skip to main content
Glama

stop_clip

Stop playback of a specific clip in Ableton Live by specifying track and clip indices.

Instructions

Stop playing a clip.

Parameters:

  • track_index: The index of the track containing the clip

  • clip_index: The index of the clip slot containing the clip

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
track_indexYes
clip_indexYes

Implementation Reference

  • The actual handler implementation in the Ableton Remote Script that interacts with the Ableton Live object model to stop the clip.
    def _stop_clip(self, track_index, clip_index):
        """Stop a clip"""
        try:
            if track_index < 0 or track_index >= len(self._song.tracks):
                raise IndexError("Track index out of range")
            
            track = self._song.tracks[track_index]
            
            if clip_index < 0 or clip_index >= len(track.clip_slots):
                raise IndexError("Clip index out of range")
            
            clip_slot = track.clip_slots[clip_index]
            
            clip_slot.stop()
  • The MCP tool definition and entry point that dispatches the 'stop_clip' command to the Ableton Remote Script via _run.
    def stop_clip(ctx: Context, track_index: int, clip_index: int) -> str:
        """
        Stop playing a clip.
    
        Parameters:
        - track_index: The index of the track containing the clip
        - clip_index: The index of the clip slot containing the clip
        """
        try:
            _run("stop_clip", {"track_index": track_index, "clip_index": clip_index})
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the action ('Stop playing') but doesn't explain what happens when a clip is stopped (e.g., does it reset to beginning, trigger follow actions, affect transport?), whether this requires specific permissions, or what the expected outcome is. This is inadequate for a mutation tool with zero annotation coverage.

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

Conciseness4/5

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

The description is efficiently structured with a clear purpose statement followed by parameter explanations. Every sentence serves a purpose, though the parameter section could be slightly more integrated with the main description rather than appearing as a separate list.

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 mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what 'stopping' a clip means behaviorally, what the expected outcome is, whether there are side effects, or how this interacts with other playback controls. The parameter explanations help but don't compensate for the overall lack of operational context.

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?

The description lists both parameters and explains their purpose (track_index identifies the track, clip_index identifies the clip slot), adding meaningful context beyond the schema's 0% description coverage. However, it doesn't provide details about valid ranges, indexing conventions (0-based vs 1-based), or what happens with invalid indices, leaving some gaps.

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 verb ('Stop playing') and resource ('a clip'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'stop_playback' which might stop overall playback rather than a specific clip, leaving some ambiguity about when to choose this tool over alternatives.

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_playback' or 'fire_clip'. There's no mention of prerequisites, context requirements, or typical use cases, leaving the agent with minimal usage direction.

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/FreeRiverHouse/ableton-flow'

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