Skip to main content
Glama

mcp_opendaw_move_section

Move all regions within a beat range to a new position, replacing multiple delete and create steps with a single non-destructive operation for restructuring arrangements.

Instructions

Move all regions within a beat range to a new position (non-destructive rearrangement).

Scans all tracks across all specified audio units, finds every region that overlaps the [from_beat, to_beat) range, and moves each one to target_beat with the same relative offset. Unlike duplicate_section, this removes the original — a true cut-and-paste operation.

This is the arrangement tool for restructuring: "move the bridge from bar 33 to bar 17" or "shift this 4-bar fill 8 bars earlier". One call replaces N delete + N create sequences.

from_beat: Start of the source section in beats. to_beat: End of the source section in beats (exclusive). target_beat: Where to move the section (beat 0 = start of project). unit_indices: Comma-separated AU indices to scan (default: all AUs).

Returns number of regions moved, per-track details, and old/new positions.

Examples: move_section(from_beat=32, to_beat=48, target_beat=16) -> Move bars 9-12 to bar 5 (shift 16 beats earlier) move_section(from_beat=0, to_beat=16, target_beat=32, unit_indices="0,1") -> Move first 4 bars from AUs 0,1 to beat 32

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
to_beatYes
from_beatYes
target_beatYes
unit_indicesNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description carries full burden and details the non-destructive nature, scanning all tracks across audio units, moving with relative offset, and returning counts. It does not fully disclose if automation or other data is moved, or potential limitations, but overall it is highly transparent.

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 with a concise first sentence and a clear breakdown of parameters and examples. While somewhat lengthy, every sentence adds value and no extraneous information is present.

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?

Given the presence of an output schema (though not shown), the description adequately covers use cases, parameters, and return value summary. It does not address error conditions or edge cases, but for a moderately complex tool, it provides sufficient context for an agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite 0% schema description coverage, the description explains all four parameters in detail: from_beat, to_beat (exclusive), target_beat (beat 0=start), and unit_indices (default all). Examples further clarify usage, fully compensating for the lack of schema descriptions.

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 moves all regions within a beat range to a new position, specifying it's a cut-and-paste operation. It distinguishes from duplicate_section by noting it removes the original, and provides concrete examples like 'move the bridge from bar 33 to bar 17', making the purpose unambiguous.

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 explicitly contrasts with duplicate_section and notes it replaces multiple delete+create sequences, giving clear when-to-use guidance. However, it lacks explicit when-not-to-use or prerequisites, though the context is sufficient for an agent to make informed decisions.

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