Live Maestro

Overview Schema Source Related Servers Discussions Admin

delete_clip

Destructive

Delete a Session clip along with its notes and envelopes. Confirm to execute; without confirmation, previews what would be removed.

Instructions

Delete the clip in a Session slot, its notes and envelopes with it.

Requires confirm=True. With confirm=False it reports the clip name, length and
note count that the call would remove, and changes nothing.

Returns:
    Dictionary reporting the deletion, or the loss report when unconfirmed.

Note:
    This empties one Session slot. Slot indices do not shift, so nothing else
    moves and no other index goes stale.

    Emptying a clip is not the same as deleting it: write_clip_notes with an
    empty list and mode='replace' leaves the clip in place with its length,
    loop and envelopes intact. Prefer that where the slot should stay filled.
    A clip already copied into the Arrangement by arrange is a separate clip and
    survives this.

Input Schema

TableJSON Schema

Name	Required	Description
`path`	No	LOM path to a Session clip, song.tracks[N].clip_slots[M] with or without a trailing .clip, as an alternative to track and slot. A song.tracks[N].arrangement_clips[i] path is refused with code region_not_addressable.
`slot`	No	Clip slot index in track.clip_slots, counted from 0, which is the scene the clip sits in. Give track and slot, or give path instead. These are Session coordinates; an Arrangement clip has none.
`track`	No	Session track index in song.tracks, counted from 0. Give track and slot, or give path instead. These are Session coordinates; an Arrangement clip has none.
`confirm`	No	True carries the removal out. False changes nothing and returns a report of what the call would remove, which is how to look before committing to it.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedSep 24, 2026

addedInput schema / properties / path

Added value: +{
+  "default": "",
+  "description": "LOM path to a Session clip, song.tracks[N].clip_slots[M] with or without a trailing .clip, as an alternative to track and slot. A song.tracks[N].arrangement_clips[i] path is refused with code region_not_addressable.",
+  "title": "Path",
+  "type": "string"
+}

addedInput schema / properties / slot / anyOf

Added value: +[
+  {
+    "minimum": 0,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / slot / default
```
Added value: +null
```

changedInput schema / properties / slot / description

Previous value: -"Clip slot index in track.clip_slots, counted from 0. A slot index is the scene the clip sits in, so slot 2 is the third scene down."New value: +"Clip slot index in track.clip_slots, counted from 0, which is the scene the clip sits in. Give track and slot, or give path instead. These are Session coordinates; an Arrangement clip has none."

removedInput schema / properties / slot / type
```
Removed value: -"integer"
```

addedInput schema / properties / track / anyOf

Added value: +[
+  {
+    "minimum": 0,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / track / default
```
Added value: +null
```

changedInput schema / properties / track / description

Previous value: -"Track index in song.tracks, counted from 0."New value: +"Session track index in song.tracks, counted from 0. Give track and slot, or give path instead. These are Session coordinates; an Arrangement clip has none."

removedInput schema / properties / track / type
```
Removed value: -"integer"
```

removedInput schema / required

Removed value: -[
-  "track",
-  "slot"
-]

Changed3 schema fields changedv0.1.1Sep 7, 2026

addedInput schema / properties / confirm / description

Added value: +"True carries the removal out. False changes nothing and returns a report of what the call would remove, which is how to look before committing to it."

addedInput schema / properties / slot / description

Added value: +"Clip slot index in track.clip_slots, counted from 0. A slot index is the scene the clip sits in, so slot 2 is the third scene down."

addedInput schema / properties / track / description

Added value: +"Track index in song.tracks, counted from 0."

First observedv0.1.0Sep 5, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already include destructiveHint=true and readOnlyHint=false, but the description goes well beyond them: it states that slot indices do not shift, that confirm=False only reports without changing anything, and that clips copied into the Arrangement are independent and survive. This reveals side effects and safety behavior that annotations cannot convey.

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 well-structured with clear headings (Requires, Returns, Note), front-loads the core action, and every sentence earns its place by conveying either a safety requirement, an edge case, or an alternative. Despite moderate length, there is no fluff, and the organization makes scanning easy.

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

Completeness5/5

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

The description covers the full calling context: intended effect, safety mechanism (confirm=True), return values, side effects on slot indices, relationship to write_clip_notes, and behavior of Arrangement copies. An agent has everything needed to invoke the tool correctly and safely, especially with an output schema also present.

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?

Schema description coverage is 100%, so the schema already documents all four parameters thoroughly. The description does not add significant parameter-level detail beyond what the schema provides; it mostly restates the confirm behavior and path/track/slot alternatives already present in the schema. Baseline 3 is appropriate.

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 opens with a specific verb+resource: 'Delete the clip in a Session slot, its notes and envelopes with it.' This distinguishes the tool from siblings like delete_track, create_clip, and write_clip_notes. It names what is removed (clip, notes, envelopes) and where (Session slot), leaving no ambiguity.

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

Usage Guidelines5/5

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

The description explicitly tells when to prefer an alternative: 'Emptying a clip is not the same as deleting it: write_clip_notes with an empty list and mode='replace' leaves the clip in place... Prefer that where the slot should stay filled.' It also warns that an Arrangement copy survives deletion, helping an agent choose correctly. The confirm=True requirement is clearly stated as a precondition for actual removal.

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