Skip to main content
Glama

delete_track

Removes a specified track and all its contents from the Ableton Live set, then shifts later tracks up one index. Requests confirmation before deletion.

Instructions

Remove a track and everything on it. Ask the user first. Tracks after it move up one index.

Parameters:

  • track_index: The track to remove

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 observedv2.1.1

TDQS

A3.5/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 and does real work: it discloses the cascading destruction of track contents and the index-shift side effect on subsequent tracks, both of which the agent could not guess. It stops short of stating whether the deletion is undoable or what happens to clips routed elsewhere, which matters for an irreversible 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?

Purpose, safety caveat, and side effect are each one short sentence, front-loaded in the order an agent needs them, then a compact parameter block. Nothing is padded or repeated.

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

Completeness3/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 no explanation, and the destructive side effects are covered. However, for an irreversible mutation with zero annotation coverage and an undocumented integer parameter, the missing index-base convention and undo story leave a real gap an agent must guess at.

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% – the single parameter is bare ('Track Index', integer, no description) – so the description must compensate, but 'The track to remove' merely restates the name. It never resolves whether the index is zero- or one-based, or how the agent should obtain a valid index (e.g. via get_track_info or arrangement_overview).

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 first sentence gives a specific verb plus resource ('Remove a track') and immediately scopes the blast radius ('and everything on it'), which separates it from clip- or scene-level deletions like delete_clip. It never names a sibling explicitly, so the differentiation is inferable rather than stated.

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?

'Ask the user first' is a confirmation requirement, not selection guidance; it tells the agent how to behave before calling, not when this tool is the right choice over delete_clip or delete_scene. Usage against its siblings is only implied by the resource noun in the name.

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