List clip slots and clips for one exact track, including arm/freeze recording readiness and native one-shot launch quantization choices.
List clip slots and clips on one exact track, including arm/freeze recording readiness and native one-shot launch quantization choices.
| Name | Required | Description | Default |
|---|---|---|---|
| trackId | Yes | ID from list_tracks. |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.3.1Output schema / additionalPropertiesRemoved value: -trueOutput schema / anyOfAdded value: +[
+ {
+ "properties": {
+ "clips": {
+ "items": {
+ "properties": {
+ "durationUnit": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "hasClip": {
+ "type": "boolean"
+ },
+ "id": {
+ "type": "string"
+ },
+ "isPlaying": {
+ "type": "boolean"
+ },
+ "isRecording": {
+ "type": "boolean"
+ },
+ "isTriggered": {
+ "type": "boolean"
+ },
+ "lengthBeats": {
+ "anyOf": [
+ {
+ "type": "number"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "lengthSeconds": {
+ "anyOf": [
+ {
+ "type": "number"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "name": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ }
+ },
+ "required": [
+ "id",
+ "name"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "stateVersion": {
+ "minimum": 1,
+ "type": "integer"
+ },
+ "trackId": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "stateVersion",
+ "clips"
+ ],
+ "type": "object"
+ },
+ {
+ "properties": {
+ "error": {
+ "properties": {
+ "message": {
+ "type": "string"
+ },
+ "outcome": {
+ "enum": [
+ "unknown",
+ "not_executed"
+ ]
+ }
+ },
+ "required": [
+ "message",
+ "outcome"
+ ],
+ "type": "object"
+ }
+ },
+ "required": [
+ "error"
+ ],
+ "type": "object"
+ }
+]v0.3.0Input schema / properties / trackId / descriptionPrevious value: -"Stable track ID returned by list_tracks."New value: +"ID from list_tracks."Output schema / (root)Previous value: -nullNew value: +{
+ "additionalProperties": true,
+ "type": "object"
+}v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, non-destructive, and non-open-world, so the safety profile is covered. The description adds useful content about what the listing surfaces (arm/freeze readiness, launch quantization choices), but does not go deeper on pagination or ordering behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One front-loaded sentence with no filler; the verb and scope lead, and the trailing clause about recording readiness and launch quantization earns its place as genuine content. Slightly dense, but efficient.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a single-parameter, read-only listing tool with an output schema and full annotation coverage, the description supplies the needed scope and content hints. Nothing critical is missing; only pagination/ordering detail is absent, and that is minor given the output schema.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% and the single parameter (trackId, 'ID from list_tracks') is fully documented in the schema, so the baseline is 3. The description's 'one exact track' phrasing reinforces the single-track constraint but adds no new parameter semantics.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a clear verb ('List') and resource ('clip slots and clips') and scopes it to 'one exact track,' which separates it from related listing tools such as list_arrangement_clips or list_scenes. It does not name a specific sibling as an alternative, so it stops short of a 5.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is only implied: the 'one exact track' scoping and the required trackId suggest when this tool applies, but there is no explicit when-to-use/when-not guidance or named alternative. Adequate but leaves the agent to infer the boundary against list_arrangement_clips and similar tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.