Skip to main content
Glama

mcp_opendaw_set_clip_playback

Set loop, reverse, and speed playback parameters for a specific clip. Control looping, reverse playback, and speed multiplier to adjust how the clip is played.

Instructions

Set clip playback parameters (loop, reverse, speed) on a clip.

Clips have a ClipPlaybackFields (triggerMode) object with:

  • loop: Whether the clip loops (true/false)

  • reverse: Play in reverse (true/false)

  • speed: Playback speed multiplier (1 = normal)

  • quantise: Quantise value

  • trigger: Trigger mode

Pass None for any parameter to skip changing it.

unit_index: Audio unit index. track_index: Track index. clip_index: Clip index (from list_clips). loop: Enable looping (None = skip). reverse: Reverse playback (None = skip). speed: Speed multiplier (None = skip).

Returns updated playback values.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
loopYes
speedYes
reverseYes
clip_indexYes
unit_indexYes
track_indexYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations are provided, so the description must cover behavioral traits. It discloses the tool modifies clip state, allows skipping parameters, and returns updated values. This is sufficient for a setter, though it doesn't discuss error handling or side effects.

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 description is well-structured: an introductory sentence, explanation of ClipPlaybackFields, how to skip parameters, and a parameter list. It is succinct without being overly verbose, though it could be streamlined slightly.

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

Completeness3/5

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

The description mentions returns of updated playback values, which helps with completeness. However, it lacks details on error conditions, such as invalid indices or clip not found. Given the tool has 6 required parameters and no output schema, the context is adequate but not fully robust.

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?

With 0% schema coverage (the description does not echo schema titles verbatim), it adds meaning by explaining each parameter: unit_index as audio unit index, clip_index from list_clips, and the meaning of loop, reverse, speed. This goes beyond the schema's minimal titles.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool sets clip playback parameters (loop, reverse, speed) on a clip, using a specific verb-resource structure. It distinguishes from siblings like set_clip_mute or set_clip_hue by focusing on playback-specific fields.

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?

The description explains how to skip parameters by passing None and defines indices (unit_index, track_index, clip_index). While it doesn't explicitly compare to alternatives like schedule_clip_play, the context is clear enough for an agent to identify when to use this tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AMEOBIUS-team/opendaw-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server