ableton-mcp

by ku1x

Overview Schema Source Related Servers Score Discussions Admin

Python

Local

clear_notes_from_clip

Remove all MIDI notes from a specified Session clip. Use before adding edited notes to replace a clip's contents.

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)

Input Schema

TableJSON Schema

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

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.4.0Sep 9, 2026

TDQS

A4.6/5.0

Behavior4/5

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

No annotations are present, so the description must carry the safety burden itself. It clearly states the operation removes all MIDI notes and, crucially, explains the additive behavior of the sibling tool. It does not explicitly state irreversibility or side effects on undo/history, which keeps it short of a 5.

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?

Three tight sentences: what the tool does, the key behavioral caveat, and the recommended workflow. No filler.

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?

The description covers the operation, the critical write behavior, and the companion tools needed to use it safely. Output schema handles return expectations, so nothing essential is missing; minor omission is whether the operation is undoable.

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?

The schema provides only titles, and schema description coverage is 0%. The description compensates by explaining what each parameter refers to, including the user_prompt telemetry purpose.

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?

Starts with an unambiguous action: “Remove all MIDI notes from a Session clip.” The verb, object, and scope are all explicit, and the read-modify-write context distinguishes it from add_notes_to_clip and get_clip_notes.

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?

Provides concrete workflow guidance: clear the clip first, then repopulate with add_notes_to_clip, because add_notes_to_clip only appends. This tells the agent exactly when and how to use the tool in combination with siblings.

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