Remove a scene row and its clips from your Ableton Live set to clear unused sections and keep the Session view organized.
Delete a scene row and its clips.
| Name | Required | Description | Default |
|---|---|---|---|
| scene_index | Yes |
Changes observed during successful MCP inspections.
v1.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full behavioral disclosure. It usefully states that clips are also deleted, which is important cascade information beyond the schema. However, it omits permission requirements, irreversibility, and whether confirmation is needed for a destructive operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single front-loaded sentence with no filler. It efficiently conveys the core action and the cascade effect, so every part earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a destructive, unannotated tool with a required parameter and no output schema, the description is too sparse. It does not explain how to specify the scene_index or cover the risks of an irreversible deletion, leaving an agent without essential context to call it correctly and safely.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% and the description says nothing about scene_index—not its meaning, expected range, whether it is zero-based, or how to identify the target scene. The schema only provides the parameter name and integer type, so the description fails to compensate for the documentation gap.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource: 'Delete a scene row and its clips.' It is clear enough to distinguish from siblings like delete_clip and delete_track by naming the scene row and the cascade to its clips. However, it does not explicitly contrast with those siblings, so it falls short of the highest clarity tier.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description offers no guidance on when to use this tool versus alternatives such as delete_clip or duplicate_scene. Usage is only implied by the tool name and the word 'Delete.' There are no exclusions, prerequisites, or conditions provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.