Skip to main content
Glama
Sign In
ableton-mcp

ableton-mcp

by mrinalghosh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

create_midi_clip

Create a MIDI clip and populate it with specified notes to turn musical ideas into an Ableton Live set.

Instructions

Create a MIDI clip and fill with notes. Use this when the user wants a musical idea written into the set.

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": "<track>",
      "clip_slot": "<clip_slot>",
      "length_beats": "<length_beats>",
      "notes": "<notes>"
    },
    "name": "create_midi_clip"
  }
}

Input Schema

NameRequiredDescriptionDefault
trackYes
clip_slotYes
length_beatsYes
notesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are present, so the description must disclose behavior. It mentions creating and filling but does not explain whether it overwrites existing clips, what happens if the slot is occupied, or any side effects like selection changes.

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 very concise with two sentences and no redundant information. It could be improved by adding more detail without becoming verbose.

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

Completeness2/5

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

Given 4 required parameters, no output schema, and no annotations, the description lacks essential details. It does not explain the note object structure, constraints on clip_slot, or length_beats format, making it incomplete for reliable use.

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?

The input schema has 0% description coverage, yet the description only adds 'fill with notes' to explain the notes parameter. It does not clarify the meaning of track or clip_slot, nor the structure of note objects, leaving significant ambiguity.

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

Purpose4/5

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

The description clearly states the tool creates a MIDI clip and fills it with notes. This distinguishes it from sibling tools like fire_clip or modify_clip_notes, as it focuses on creation with content.

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

Usage Guidelines3/5

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

The description says to use it when the user wants a musical idea written into the set, providing some context. However, it does not explicitly contrast with alternatives like modify_clip_notes or specify when not to use it.

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