ableton-mcp

Overview Schema Source Related Servers Discussions Admin

get_parameter_automation_context

Read-onlyIdempotent

Inspect device parameters and mixer controls on a track, Group, Return, or Main to list options or read one observed ID and confirm native automation support.

Instructions

Read discoverable device parameters or mixer controls and native automation handoff support on an exact track, Group, Return or Main. Omit parameterId to list, supply one observed ID for a target read. Unsupported controls remain explicit. Read-only; all profile.

Input Schema

Name	Required	Description
`trackId`	Yes	track-N from list_tracks, return-N from get_set_mixer, or master.
`deviceId`	No	ID from list_devices.
`parameterId`	No	Observed parameter-N for a device, or a mixer control ID from this read. Omit deviceId for mixer controls.

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: +[
+  {
+    "properties": {
+      "clipId": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "controls": {
+        "items": {
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "deviceId": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "deviceName": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "frozen": {
+        "anyOf": [
+          {
+            "type": "boolean"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "identityToken": {
+        "type": "string"
+      },
+      "parameterId": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "reason": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "setFingerprint": {
+        "type": "string"
+      },
+      "stateVersion": {
+        "minimum": 1,
+        "type": "integer"
+      },
+      "status": {
+        "type": "string"
+      },
+      "supported": {
+        "type": "boolean"
+      },
+      "trackId": {
+        "type": "string"
+      },
+      "transport": {
+        "type": "object"
+      }
+    },
+    "required": [
+      "stateVersion"
+    ],
+    "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.9/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds a real behavioral trait: unsupported controls are surfaced explicitly rather than silently dropped, so the agent knows to expect negative results in the payload. The trailing 'all profile' is opaque jargon that conveys no usable behavior.

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?

The verb and scope are front-loaded, and the mode rule follows immediately with no filler. The closing fragment 'Read-only; all profile' is redundant with readOnlyHint and partially unintelligible, costing a perfect score.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With a complete schema, full annotations, and an output schema, the description only needs to convey scope, mode selection, and safety; it does all three. Return values are covered by the output schema, so no further detail is owed.

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 100%, so the baseline is 3, but the description adds a mode semantic the schema does not state: omitting parameterId switches to list mode versus supplying an 'observed' ID for a target read. This correctly signals that a prior read is required to obtain a valid ID, which the schema only implies with 'Observed parameter-N'.

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 ('Read') with specific resources: discoverable device parameters, mixer controls, and native automation handoff support, scoped to an exact track/Group/Return/Main. It is distinguishable in substance, but it never names the closely related siblings (list_device_parameters, get_selected_parameter_context, get_automation_capabilities), leaving the agent to disambiguate by inference.

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?

'Omit parameterId to list, supply one observed ID for a target read' gives clear mode selection for the two call shapes. However, there is no guidance on when to choose this tool over list_device_parameters or get_selected_parameter_context, nor any prerequisite ordering for obtaining observed IDs.

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

Deploy Server