Skip to main content
Glama
Sign In
Ableton MCP Extended

Ableton MCP Extended

by zabolotniydj
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

create_audio_track

Add a new audio track to an Ableton Live session at a specified insert position, defaulting to the end of the track list.

Instructions

Create a new audio track.

Parameters:

  • index: Insert position (-1 = end of list).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_audio_track"
  }
}

Input Schema

NameRequiredDescriptionDefault
indexNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of exposing side effects, permissions, or state changes. It only states the basic action without mentioning any side effects, such as how the track is added to the session or what happens if the index is out of range.

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 concise and to the point, with a clear sentence for the tool's purpose and a separate explanation for the parameter. No unnecessary information or redundancy.

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?

The description is very sparse. It does not mention return values (even though the tool likely returns something), side effects, or any related context. Given that the tool creates an audio track, more detail about what happens to the track or how it integrates with the session would be expected.

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 parameter 'index' is well-documented: the description clarifies that -1 means end of list, which complements the schema's default value. This is clear and sufficient for a single parameter.

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 clearly states the tool's purpose: creating a new audio track. It distinguishes well from sibling tools like create_midi_track and create_scene by specifying the track type.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool over alternatives. It does not mention prerequisites, typical use cases, or when to prefer create_audio_track over create_midi_track or other creation tools.

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