Skip to main content
Glama

delete_clip

Remove audio or MIDI clips from Ableton Live tracks by specifying track and clip indices to clean up arrangements and manage session content.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
track_indexYes
clip_indexYes

Implementation Reference

  • The MCP tool handler for 'delete_clip'. It connects to the Ableton remote script and sends a 'delete_clip' command with track_index and clip_index parameters, returning success or error message.
    @mcp.tool()
    def delete_clip(ctx: Context, track_index: int, clip_index: int) -> str:
        try:
            ableton = get_ableton_connection()
            result = ableton.send_command("delete_clip", {"track_index": track_index, "clip_index": clip_index})
            return f"Deleted clip '{result.get('clip_name')}' from track '{result.get('track_name')}'"
        except Exception as e:
            logger.error(f"Error deleting clip: {str(e)}")
            return f"Error deleting clip: {str(e)}"
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

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

Parameters1/5

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

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

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/Milesy1/MCP-Ableton-API'

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