ableton-mcp

Overview Schema Source Related Servers Discussions Admin

read_production_artifact

Read-onlyIdempotent

Read a bounded page of a private project artifact by project ID and artifact ID, then follow nextOffset to retrieve more detail; truncated pages are not complete evidence.

Instructions

Read a bounded page of one private project artifact. Follow nextOffset for more detail; truncated pages are not complete evidence.

Input Schema

Name	Required	Description
`limit`	No
`offset`	No
`projectId`	Yes	Private project namespace.
`artifactId`	Yes	Artifact ID returned by a producer tool.

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": {
+      "artifactId": {
+        "pattern": "^[a-f0-9]{64}$",
+        "type": "string"
+      },
+      "nextOffset": {
+        "anyOf": [
+          {
+            "minimum": 0,
+            "type": "integer"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "offset": {
+        "minimum": 0,
+        "type": "integer"
+      },
+      "text": {
+        "type": "string"
+      },
+      "totalCharacters": {
+        "minimum": 0,
+        "type": "integer"
+      },
+      "truncated": {
+        "type": "boolean"
+      }
+    },
+    "required": [
+      "artifactId",
+      "text",
+      "offset",
+      "totalCharacters",
+      "truncated",
+      "nextOffset"
+    ],
+    "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?

Annotations already establish readOnly, idempotent, non-destructive and closed-world. The description adds genuinely new behavior: results are paginated and a truncated page must not be treated as complete evidence, which is an important reasoning constraint for an agent. It stops short of describing return structure or error behavior.

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?

Two short sentences, zero filler, with the core read action front-loaded and the paging caveat immediately after. Nothing is redundant.

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 explanation, and annotations cover the safety profile. The remaining gap is that 'nextOffset' is referenced without stating it comes from the response, and no guidance on choosing a limit is given.

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 50%: projectId and artifactId are documented, while limit and offset are not. The description hints that pages continue via 'nextOffset', which clarifies the paging parameter's role, but it introduces a name that does not exist in the input schema and does not explain limit bounds or offset units. Baseline 3 for partial coverage with marginal added meaning.

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') and resource ('one private project artifact') with the scope qualifier 'bounded page', so an agent can tell this is a paginated artifact reader. It does not name a sibling alternative to sharpen the distinction, but none of the nearby tools obviously overlap.

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?

The sentence 'truncated pages are not complete evidence' implies usage (keep paging until complete) but never states when this tool should be chosen over another or what preconditions apply beyond 'Artifact ID returned by a producer tool' in the schema. Usage is implied rather than prescribed.

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

Deploy Server