ableton-mcp

Overview Schema Source Related Servers Discussions Admin

advance_production_session

Destructive

Advance one durable Ableton production session phase using revision checks and guarded actions, so proposals, choices, apply, resume, replan, feedback, and evaluation stay consistent.

Instructions

Advance one durable session phase with optimistic revision checks. propose runs a bounded specialist; choose selects a saved creative alternative; apply retains original dry-run and confirmation guards. resume inspects fresh state and preserves uncertain or partially failed execution. replan explicitly starts a new proposal from that inspection and its saved ledger. evaluate uses listening or caller-postcondition completion. Interrupted execution is never replayed.

Input Schema

Name	Required	Description
`text`	No	Listening feedback for feedback, or an explicit remaining goal for replan; not an observed Live fact.
`action`	Yes
`dryRun`	No
`decision`	No
`planHash`	No	Original tool's plan hash.
`projectId`	Yes	Private project namespace.
`sessionId`	Yes	Durable session ID returned by start_production_session.
`constraints`	No
`alternativeIndex`	No
`expectedRevision`	Yes
`confirmationToken`	No	Original tool's single-use confirmation token.
`expectedStateVersion`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv0.3.1Oct 23, 2026

changedInput schema / properties / action / enum

Previous value: -[
-  "resume",
-  "propose",
-  "choose",
-  "apply",
-  "feedback",
-  "evaluate"
-]New value: +[
+  "resume",
+  "replan",
+  "propose",
+  "choose",
+  "apply",
+  "feedback",
+  "evaluate"
+]

addedInput schema / properties / constraints

Added value: +{
+  "items": {
+    "description": "Explicit user constraint.",
+    "maxLength": 2000,
+    "minLength": 1,
+    "type": "string"
+  },
+  "maxItems": 12,
+  "type": "array"
+}

changedInput schema / properties / text / description

Previous value: -"Explicit user listening feedback; not an observed Live fact."New value: +"Listening feedback for feedback, or an explicit remaining goal for replan; not an observed Live fact."

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

addedOutput schema / anyOf

Added value: +[
+  {
+    "properties": {
+      "audibleQualityVerified": {
+        "const": false
+      },
+      "execution": {
+        "properties": {
+          "counts": {
+            "additionalProperties": {
+              "maximum": 16,
+              "minimum": 0,
+              "type": "integer"
+            },
+            "type": "object"
+          },
+          "operations": {
+            "items": {
+              "properties": {
+                "attemptRef": {
+                  "pattern": "^[a-f0-9]{64}$",
+                  "type": "string"
+                },
+                "error": {
+                  "maxLength": 300,
+                  "type": "string"
+                },
+                "index": {
+                  "maximum": 15,
+                  "minimum": 0,
+                  "type": "integer"
+                },
+                "nativeStatus": {
+                  "enum": [
+                    "applied",
+                    "outcome_unknown",
+                    "postconditions_failed",
+                    "pending_postconditions",
+                    "pending_user_action"
+                  ]
+                },
+                "receiptId": {
+                  "pattern": "^[a-f0-9]{64}$",
+                  "type": "string"
+                },
+                "resultRef": {
+                  "pattern": "^[a-f0-9]{64}$",
+                  "type": "string"
+                },
+                "status": {
+                  "enum": [
+                    "not_attempted",
+                    "execution_pending",
+                    "applied",
+                    "rejected",
+                    "outcome_unknown",
+                    "postconditions_failed",
+                    "pending_postconditions",
+                    "pending_user_action",
+                    "unrecorded"
+                  ]
+                },
+                "tool": {
+                  "type": "string"
+                }
+              },
+              "required": [
+                "index",
+                "tool",
+                "status"
+              ],
+              "type": "object"
+            },
+            "maxItems": 16,
+            "type": "array"
+          },
+          "taskId": {
+            "pattern": "^[a-f0-9]{64}$",
+            "type": "string"
+          }
+        },
+        "required": [
+          "taskId",
+          "operations",
+          "counts"
+        ],
+        "type": "object"
+      },
+      "phase": {
+        "enum": [
+          "inspect",
+          "choose",
+          "propose",
+          "proposing",
+          "apply",
+          "execution_pending",
+          "needs_inspection",
+          "audition",
+          "evaluate",
+          "complete"
+        ]
+      },
+      "recoveryRef": {
+        "pattern": "^[a-f0-9]{64}$",
+        "type": "string"
+      },
+      "recoveryRequired": {
+        "type": "boolean"
+      },
+      "revision": {
+        "minimum": 1,
+        "type": "integer"
+      },
+      "sessionId": {
+        "type": "string"
+      },
+      "sessionRef": {
+        "pattern": "^[a-f0-9]{64}$",
+        "type": "string"
+      }
+    },
+    "required": [
+      "sessionId",
+      "sessionRef",
+      "revision",
+      "phase",
+      "audibleQualityVerified"
+    ],
+    "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

A3.8/5.0

Behavior4/5

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

Goes well beyond the annotations: 'optimistic revision checks' discloses the concurrency contract, 'apply retains original dry-run and confirmation guards' discloses the mutation safeguards, and 'Interrupted execution is never replayed' explains the non-idempotency that idempotentHint=false only implies. It does not spell out auth/permission requirements or what destructive effects actually occur.

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 purpose, then a dense sequence of action-specific clauses, each carrying distinct information with no filler. The single-run-on style makes it slightly hard to scan but no sentence is wasted.

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?

For a 12-parameter destructive mutation with only 42% schema coverage, the description covers the action semantics and key safety traits well, and the output schema removes the need to explain returns. However, the unexplained 'feedback' action and undocumented revision/decision/token parameters leave gaps an agent must guess at.

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 only 42%, so the description should carry more load. It does define six of the seven action enum values in prose (useful, since the schema gives no description for 'action'), but it omits the 'feedback' action entirely and says nothing about expectedRevision, expectedStateVersion, decision, planHash, or confirmationToken. Partial compensation only.

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 ('Advance one durable session phase') and immediately qualifies it with the concurrency model ('optimistic revision checks'). An agent can tell this is the phase-progression driver of a session workflow, distinct from start_/get_production_session. It does not name a sibling explicitly, so it falls short of 5.

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?

The description routes the agent across the action enum, giving a condition for each: propose for a bounded specialist, choose for a saved alternative, resume for inspection of fresh state, replan for a new proposal, evaluate for completion. This is genuine when-to-use guidance. It lacks explicit when-not-to-use framing against sibling session tools.

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

Deploy Server