ableton-mcp

Overview Schema Source Related Servers Discussions Admin

set_session_clip_entry

Destructive

Set one inactive Session launch entry in explicit units: separate MIDI/warped marker, or unwarped nonlooped range start. Retains the end, repeating loop and exposed material.

Instructions

Set one inactive Session launch entry in explicit units: separate MIDI/warped marker, or unwarped nonlooped range start. Retains the end, repeating loop and exposed material. Binds native identity/content/controls; refuses recording, arms, frozen targets and pending launches. Reports partial work without rollback or replay. Does not launch or rewrite notes/files. Updated bridge; all profile.

Input Schema

Name	Required	Description
`unit`	Yes	Active entry unit from the native plan: MIDI/warped audio beats, unwarped audio seconds.
`start`	Yes	Finite absolute clip position strictly before the retained end marker; seconds must be nonnegative.
`clipId`	Yes	Exact populated Session clip ID.
`dryRun`	No	False executes with token and hash.
`trackId`	Yes	ID from list_tracks.
`planHash`	No	Plan hash.
`confirmationToken`	No	Single-use plan token.
`expectedStateVersion`	Yes	Observed stateVersion.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.3.1Oct 23, 2026

removedOutput schema / additionalProperties
```
Removed value: -true
```

addedOutput schema / anyOf

Added value: +[
+  {
+    "oneOf": [
+      {
+        "properties": {
+          "confirmation": {
+            "properties": {
+              "expiresAt": {
+                "type": "number"
+              },
+              "planHash": {
+                "pattern": "^[a-f0-9]{64}$",
+                "type": "string"
+              },
+              "token": {
+                "minLength": 1,
+                "type": "string"
+              }
+            },
+            "required": [
+              "token",
+              "planHash",
+              "expiresAt"
+            ],
+            "type": "object"
+          },
+          "dryRun": {
+            "const": true
+          },
+          "plan": {
+            "type": "object"
+          }
+        },
+        "required": [
+          "dryRun",
+          "plan",
+          "confirmation"
+        ],
+        "type": "object"
+      },
+      {
+        "properties": {
+          "dryRun": {
+            "const": false
+          },
+          "operationOutcome": {
+            "properties": {
+              "evidence": {
+                "items": {
+                  "type": "string"
+                },
+                "type": "array"
+              },
+              "reason": {
+                "type": "string"
+              },
+              "schemaVersion": {
+                "const": 1
+              },
+              "status": {
+                "enum": [
+                  "applied",
+                  "outcome_unknown",
+                  "postconditions_failed",
+                  "pending_postconditions",
+                  "pending_user_action"
+                ]
+              }
+            },
+            "required": [
+              "schemaVersion",
+              "status",
+              "reason",
+              "evidence"
+            ],
+            "type": "object"
+          }
+        },
+        "required": [
+          "dryRun",
+          "operationOutcome"
+        ],
+        "type": "object"
+      }
+    ],
+    "properties": {
+      "dryRun": {
+        "type": "boolean"
+      }
+    },
+    "required": [
+      "dryRun"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "error": {
+        "properties": {
+          "message": {
+            "type": "string"
+          },
+          "outcome": {
+            "enum": [
+              "unknown",
+              "not_executed"
+            ]
+          }
+        },
+        "required": [
+          "message",
+          "outcome"
+        ],
+        "type": "object"
+      }
+    },
+    "required": [
+      "error"
+    ],
+    "type": "object"
+  }
+]

Addedv0.3.0Oct 19, 2026

TDQS

B3.3/5.0

Behavior4/5

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

Beyond the annotations (destructiveHint=true, idempotentHint=false), the description adds real behavioral context: it retains the end/loop/exposed material, reports partial work without rollback or replay, and refuses certain target states. That goes meaningfully past what the structured fields convey, though the phrase "Binds native identity/content/controls" is opaque.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded and most sentences carry information (retention, refusal conditions, partial-work behavior). But the closing "Updated bridge; all profile." is meaningless filler, and the dense shorthand ("Binds native identity/content/controls") costs more clarity than it saves in length.

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?

For an 8-parameter destructive mutation with an output schema and annotations present, the description covers the key behavioral facts: what is preserved, what states are rejected, and that partial work is not rolled back. It does not need to explain return values, and remaining gaps are minor.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents unit, start, dryRun, planHash, and confirmationToken well. The description reinforces the unit semantics and the constraint that the start precedes a retained end, but adds little beyond the schema's own parameter descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb+resource is present ("Set one inactive Session launch entry in explicit units") and it distinguishes two entry modes (MIDI/warped marker vs unwarped nonlooped range start). However, "launch entry" is non-standard jargon that an agent may not map to the clip start marker, and no sibling (e.g. set_clip_timing, move_audio_warp_marker) is named to disambiguate scope.

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?

It does specify exclusions — refuses recording, arms, frozen targets, and pending launches — which is genuine when-not guidance. But there is no explicit when-to-use statement and no named alternative for the excluded cases, so an agent must infer context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server