Skip to main content
Glama
Sign In
ableton12-mcp

ableton12-mcp

by verove-jordan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

delete_track

Remove a track from your Ableton Live session. Higher track indices shift down automatically; re-read session info to refresh indexes.

Instructions

Delete a track. All higher track indices shift down — re-read get_session_info afterwards.

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>"
    },
    "name": "delete_track"
  }
}

Input Schema

NameRequiredDescriptionDefault
track_indexYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses the key side effect (higher track indices shift down) and recommends re-reading get_session_info, which is valuable behavioral context. It omits error handling but covers the main mutation.

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 a single, front-loaded sentence with no wasted words. Every phrase adds value, making it appropriately concise.

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?

Given the simple operation, existing output schema, and clear disclosure of side effects, the description is mostly complete. The only gap is lack of invalid-index handling, but that is a minor omission.

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?

Schema description coverage is 0%, and the description does not mention track_index at all. It fails to clarify whether indexing is zero-based or which track is targeted, leaving the parameter meaning entirely to the schema property name.

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 'Delete a track' with a specific verb and resource, distinguishing it from sibling tools like delete_clip, delete_device, and delete_scene.

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

Usage Guidelines4/5

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

It provides a clear usage context by explaining the index shift and telling the user to re-read get_session_info afterwards. It does not explicitly mention alternatives or when not to use, but the guidance is sufficient for the operation.

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