ableton-mcp

Overview Schema Source Related Servers Discussions Admin

get_clip_timing

Read-onlyIdempotent

Read a clip's loop, marker, and Session launch timing by trackId and clipId; returns beat/second units and supported=false if unavailable.

Instructions

Read Session/Arrangement loops and markers, plus Session launch modes. Units: MIDI/warped beats, unwarped seconds. Unavailable: supported=false.

Input Schema

Name	Required	Description	Default
`clipId`	Yes	list_clips Session ID or supported list_arrangement_clips ID.
`trackId`	Yes	ID from list_tracks.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.3.1Oct 23, 2026

changedInput schema / properties / clipId / description

Previous value: -"Session ID from list_clips; Arrangement ID from list_arrangement_clips where supported."New value: +"list_clips Session ID or supported list_arrangement_clips ID."

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

addedOutput schema / anyOf

Added value: +[
+  {
+    "properties": {
+      "clipId": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "deviceId": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "editorGrid": {
+        "type": "object"
+      },
+      "launchMode": {
+        "type": "object"
+      },
+      "launchQuantization": {
+        "type": "object"
+      },
+      "location": {
+        "type": "string"
+      },
+      "loop": {
+        "properties": {
+          "enabled": {
+            "type": "boolean"
+          },
+          "endBeats": {
+            "type": "number"
+          },
+          "endSeconds": {
+            "type": "number"
+          },
+          "startBeats": {
+            "type": "number"
+          },
+          "startSeconds": {
+            "type": "number"
+          },
+          "unit": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "enabled"
+        ],
+        "type": "object"
+      },
+      "markers": {
+        "properties": {
+          "endBeats": {
+            "type": "number"
+          },
+          "endSeconds": {
+            "type": "number"
+          },
+          "startBeats": {
+            "type": "number"
+          },
+          "startSeconds": {
+            "type": "number"
+          },
+          "supported": {
+            "type": "boolean"
+          },
+          "unit": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "supported"
+        ],
+        "type": "object"
+      },
+      "mute": {
+        "type": "object"
+      },
+      "setFingerprint": {
+        "type": "string"
+      },
+      "stateVersion": {
+        "minimum": 1,
+        "type": "integer"
+      },
+      "timeSignature": {
+        "properties": {
+          "denominator": {
+            "minimum": 1,
+            "type": "integer"
+          },
+          "numerator": {
+            "minimum": 1,
+            "type": "integer"
+          }
+        },
+        "required": [
+          "numerator",
+          "denominator"
+        ],
+        "type": "object"
+      },
+      "timeline": {
+        "anyOf": [
+          {
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "trackId": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "stateVersion"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "error": {
+        "properties": {
+          "message": {
+            "type": "string"
+          },
+          "outcome": {
+            "enum": [
+              "unknown",
+              "not_executed"
+            ]
+          }
+        },
+        "required": [
+          "message",
+          "outcome"
+        ],
+        "type": "object"
+      }
+    },
+    "required": [
+      "error"
+    ],
+    "type": "object"
+  }
+]

Changed3 schema fields changedv0.3.0Oct 19, 2026

changedInput schema / properties / clipId / description

Previous value: -"Stable clip ID: track-N:clip-M from list_clips, or track-N:arrangement-clip-M from list_arrangement_clips for tools that support Arrangement clips."New value: +"Session ID from list_clips; Arrangement ID from list_arrangement_clips where supported."

changedInput schema / properties / trackId / description

Previous value: -"Stable track ID returned by list_tracks."New value: +"ID from list_tracks."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}

First observedv0.1.0Sep 23, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds useful behavioral context beyond annotations by specifying the units used for MIDI/warped beats versus unwarped seconds and by disclosing the supported=false unavailability signal.

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?

The description is three short, front-loaded sentences with no filler. Each sentence provides distinct information: scope, units, and unavailability behavior.

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 a simple read-only tool with an output schema, two required parameters, and full schema descriptions, the description is largely complete: it states what is read, the relevant units, and the unsupported-case behavior. It could more explicitly distinguish this tool from adjacent read-only context tools, but nothing critical is missing for invocation.

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 description coverage is 100%, so trackId and clipId already have explanatory schema text. The description does not add parameter-specific meaning beyond the schema, which is acceptable at baseline when the schema carries the parameter semantics.

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?

The description states a specific read operation over Session/Arrangement loops, markers, and Session launch modes. It is clear enough to distinguish this read-oriented timing tool from the write-oriented sibling set_clip_timing, though it does not explicitly contrast with other read siblings such as get_clip_groove_context or get_audio_clip_state.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The read verb implies a general when-to-use, but the description gives no explicit guidance on when to choose this tool over alternatives like get_clip_groove_context, get_audio_clip_state, or set_clip_timing. There are no exclusions or prerequisites stated.

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

Deploy Server