LiveSession MCP

Overview Schema Source Related Servers Discussions Admin

clear_notes_from_clip

Destructive

Remove all MIDI notes from a Session clip so you can rewrite the clip by adding a new note set. Use it with note-reading and note-adding tools for read-modify-write edits.

Instructions

Remove all MIDI notes from a Session clip.

Writes are additive (add_notes_to_clip only appends), so to truly modify a clip you clear it first, then add the new notes. Use this with get_clip_notes and add_notes_to_clip for a real read -> modify -> write loop: read the notes, edit the list, clear_notes_from_clip, then add_notes_to_clip the edited notes.

Parameters:

track_index: The index of the track containing the clip
clip_index: The index of the clip slot containing the clip
user_prompt: The original user prompt that led to this tool call (for telemetry)

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": "clear_notes_from_clip"
  }
}

Input Schema

Name	Required	Description	Default
`clip_index`	Yes
`track_index`	Yes
`user_prompt`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Nov 7, 2026

TDQS

A4.5/5.0

Behavior4/5

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

The annotations already declare destructiveHint=true and readOnlyHint=false, and the description reinforces this by stating that *all* notes are removed and framing the call as the destructive half of a modify loop. It adds real context about why the destructive step exists, though it does not mention undo/recovery or behavior on non-MIDI or empty clips.

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 action is front-loaded in the first sentence, followed by rationale and workflow. The emphasis asterisks and the somewhat redundant restatement of the clear/add loop cost a little, but nothing is meaningfully padded.

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

Completeness4/5

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

An output schema exists, so return values need not be explained, and the description covers purpose, rationale, workflow, and parameters. Minor gaps remain around error cases and clip-type applicability, but an agent has what it needs to call this correctly.

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

Parameters4/5

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

Schema description coverage is 0%, so the description carries the burden and does document all three parameters, including the otherwise opaque user_prompt as telemetry data. The track_index and clip_index explanations are minimal, but they clarify that the pair identifies a clip slot within a track.

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 and resource: 'Remove all MIDI notes from a Session clip.' The scope qualifier 'all' and 'Session clip' distinguish it from delete_clip and from partial edit tools, so an agent can identify it without opening the schema.

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?

It explicitly explains that add_notes_to_clip only appends, so modification requires a clear-then-add sequence, and it names the full workflow with get_clip_notes and add_notes_to_clip. No alternative or ordering is left to inference.

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

Deploy Server