Skip to main content
Glama
cavi-ai

ableton-mcp

by cavi-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_session_clip_hold

Read-onlyIdempotent

Read a retained Session clip hold or list holds after a lost response, including command receipts, native clip IDs, playback snapshots, and cleanup errors. No input or playback changes.

Instructions

Read one retained Session clip hold, or list holds after a lost response. Reports press/release command receipts, current native clip IDs, playback snapshots and cleanup errors. No input or playback changes. Runtime state may disappear after reload; missing handles do not prove release. All profile.

Input Schema

NameRequiredDescriptionDefault
holdIdNoRetained hold ID; omit to list.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.1
    • removedOutput schema / additionalProperties
      Removed value: -true
    • addedOutput schema / anyOf
      Added value: +[
+  {
+    "properties": {
+      "cleanupErrors": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "clipId": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "deviceId": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "durationSeconds": {
+        "type": "number"
+      },
+      "elapsedSeconds": {
+        "type": "number"
+      },
+      "holdId": {
+        "type": "string"
+      },
+      "holds": {
+        "items": {
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "identityToken": {
+        "type": "string"
+      },
+      "isPlaying": {
+        "type": "boolean"
+      },
+      "isTriggered": {
+        "type": "boolean"
+      },
+      "mode": {
+        "type": "string"
+      },
+      "pressCallReturned": {
+        "type": "boolean"
+      },
+      "reason": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "releaseCallReturned": {
+        "type": "boolean"
+      },
+      "releaseRequested": {
+        "type": "boolean"
+      },
+      "setFingerprint": {
+        "type": "string"
+      },
+      "stateVersion": {
+        "minimum": 1,
+        "type": "integer"
+      },
+      "status": {
+        "type": "string"
+      },
+      "supported": {
+        "type": "boolean"
+      },
+      "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"
+  }
+]
  2. Addedv0.3.0

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations: it enumerates what the response carries (press/release command receipts, native clip IDs, playback snapshots, cleanup errors) and, critically, discloses two non-obvious caveats — runtime state may vanish on reload, and a missing handle does not prove release. That last point prevents a serious false inference by the agent.

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?

Four short sentences, front-loaded with the verb+resource and the list-mode trigger; each sentence carries distinct information (capability, read-only guarantee, caveats). 'All profile' is an opaque trailing fragment that costs a little clarity.

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 no further explanation, and the description still summarizes payload contents plus retention caveats. The only residual gap is the unexplained 'All profile' scope phrase.

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% and the schema already says 'omit to list', so the description's 'Read one ... or list holds' only restates the schema-supported behavior. Baseline 3 is appropriate when a single optional parameter is fully documented in schema.

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 ('Read one retained Session clip hold') and adds the dual mode (single read vs. list). It does not name the sibling write tools (hold_session_clip / finish_session_clip_hold), so differentiation is implied by 'Read' and 'No input or playback changes' rather than explicit.

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?

'or list holds after a lost response' gives a concrete trigger for the list mode (idempotent recovery after a failed call), and 'No input or playback changes' implicitly steers away from the mutating siblings. No explicit when-not or named alternatives, so it stops short of a 5.

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