Skip to main content
Glama

start_undo_group

Groups all changes into one undo step until end_undo_group, allowing a whole multi-step request to be reverted at once. Close the group afterward; open groups auto-close after two minutes.

Instructions

Start grouping: every change until end_undo_group becomes a single undo step, so a whole request ("8 bars of techno with a bassline") can be taken back at once. Always call end_undo_group afterwards; a group left open is closed automatically after two minutes.

Parameters:

  • name: What the group is for (shown in Live's log)

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": "start_undo_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoAbleton Studio MCP

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

A4.1/5.0
Behavior3/5

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

With no annotations at all, the description carries the full behavioral burden. It does disclose two valuable traits absent from structured data: the two-minute auto-close and that the group name surfaces in Live's log. It does not cover what happens if start is called twice while a group is open, whether nesting is supported, or what happens to grouped changes after the timeout — meaningful gaps for a stateful tool.

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?

Front-loaded with the core behavior, then the mandatory follow-up call and the timeout safeguard. The parenthetical example earns its place by illustrating what a group is for; the trailing "Parameters:" block is slightly heavier than a single optional param warrants but is not wasteful.

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?

An output schema exists, so return values need not be explained, and the two pieces an agent most needs to call this correctly — pair it with end_undo_group and expect a two-minute auto-close — are present. Only edge cases around repeated or nested starts are left uncovered.

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?

Schema coverage is 0%, so the one param is documented only here, and the description compensates well by explaining that name is a human-readable label shown in Live's log. It omits that name is optional with a default ("Ableton Studio MCP"), relying on the schema for that.

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?

States a specific verb and effect: "Start grouping: every change until end_undo_group becomes a single undo step." It names the terminating sibling and the concrete outcome (a whole request taken back at once), which is enough to distinguish it from end_undo_group and undo.

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?

Gives a clear trigger — wrapping a multi-change request such as "8 bars of techno with a bassline" — and an explicit follow-up obligation ("Always call end_undo_group afterwards"), plus the alternative of doing nothing since it auto-closes in two minutes. It stops short of stating when grouping is unnecessary (e.g. single edits) or whether groups can nest, so it is clear but not exhaustive.

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