Skip to main content
Glama
Sign In
ableton-mcp-lofifren

ableton-mcp-lofifren

by LofiFren
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

delete_clip

Clears a clip from a specified track and clip slot, leaving the slot empty. Use this to remove clips in Ableton Live.

Instructions

Delete a clip from a clip slot, leaving the slot empty.

Parameters:

  • track_index: The index of the track containing the clip

  • clip_index: The index of the clip slot to clear

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "track_index": "<track_index>",
      "clip_index": "<clip_index>"
    },
    "name": "delete_clip"
  }
}

Input Schema

NameRequiredDescriptionDefault
track_indexYes
clip_indexYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries full burden. It states 'leaving the slot empty' which adds some behavioral context, but does not disclose side effects, required permissions, or confirm if the action is reversible.

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 concise with one clear sentence and a list of parameters. It avoids redundancy but could be slightly more efficient by integrating parameter explanations into the sentence.

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 a simple deletion with two integer params and no output schema, the description provides the basic action and parameter meanings. However, it lacks error handling context, prerequisites (e.g., clip must exist), and behavioral details like undo support.

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

Parameters2/5

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

Schema coverage is 0%, so description must define parameters. It explains track_index and clip_index as indices, but does not specify valid ranges, data types in context, or potential errors, leaving the agent to guess constraints.

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

Purpose5/5

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

The description 'Delete a clip from a clip slot, leaving the slot empty' uses a specific verb (delete) and resource (clip from clip slot). It clearly distinguishes from siblings like 'remove_notes_from_clip' or 'create_clip'.

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 on when to use this tool versus alternatives. It does not mention prerequisites, limitations, or when not to use it, such as whether the clip slot must exist or if there are undo considerations.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools