Skip to main content
Glama
Sign In
LiveSession MCP

LiveSession MCP

by Uri-Rosen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

clear_clip_automation

Destructive

Remove automation from a clip in Ableton Live for one parameter, or clear all automation when the parameter is omitted.

Instructions

Clear one parameter's automation from a clip, or all of it when parameter is omitted.

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

Input Schema

NameRequiredDescriptionDefault
parameterNo
clip_indexYes
arrangementNo
track_indexYes
device_indexNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds genuinely new behavioral detail: omitting the parameter wipes ALL automation on the clip, which is a materially larger destruction scope than clearing one lane. It stops short of explaining how device_index or arrangement affect what gets cleared.

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?

A single tight sentence with the destructive all-clear caveat front-loaded and no wasted words. Nothing could be removed without losing meaning.

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?

For a destructive five-parameter mutation tool with zero schema descriptions, the definition is thin: it never explains how device_index scopes the target or what the arrangement flag switches. An output schema exists, so return values need no coverage, but the input-side gap is substantial.

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% across five parameters, so the description carries the full burden. It only explains the `parameter` argument's omission semantics and says nothing about track_index, clip_index, device_index, or arrangement, leaving four arguments undocumented in both schema and prose.

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?

States a specific verb and resource ("Clear ... automation from a clip") plus the scope variation (one parameter vs. all). It is clearly distinct from the write-side sibling set_clip_automation, though it never names that sibling explicitly.

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 implies when the all-clear behavior applies (parameter omitted), but gives no explicit guidance on when to use this tool versus set_clip_automation, or any prerequisite/ordering advice. Usage is inferable but not spelled out.

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