Skip to main content
Glama

mcp_opendaw_duplicate_section

Duplicate all regions across tracks within a beat range to a new position, preserving notes, audio, and automation. Specify from, to, and target beats.

Instructions

Duplicate all regions within a beat range to a new position.

Scans all tracks across all specified audio units, finds every region that overlaps the [from_beat, to_beat) range, and copies each one to target_beat with the same relative offset. This is the arrangement operation producers use constantly: "copy verse 1 to bar 17" or "duplicate this 8-bar section after itself".

Works with note regions, audio regions, and automation regions. Preserves all content (notes, audio, automation events).

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

Returns number of regions duplicated, per-track details, and new positions.

Examples: duplicate_section(from_beat=0, to_beat=16, target_beat=16) -> Copy first 4 bars (0-16 beats) to beat 16 (bars 5-8) duplicate_section(from_beat=0, to_beat=32, target_beat=32, unit_indices="0,1,2") -> Copy first 8 bars from AUs 0,1,2 to beat 32

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
to_beatYes
from_beatYes
target_beatYes
unit_indicesNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations provided, so description carries full burden. It states it works with note, audio, and automation regions, preserves content, and returns details. However, it does not mention potential overlapping regions or undo behavior, which would improve transparency.

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?

Description is structured with a summary, detailed explanation, parameter list, and examples. It is front-loaded with the core action. Slightly verbose but well-organized.

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 moderate complexity and no annotations, the description covers the operation, region types, parameter details, and return value. Examples enhance understanding. It is mostly complete for an agent to use correctly.

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?

Schema coverage is 0%, so description must compensate. It explains all parameters (from_beat, to_beat, target_beat, unit_indices), notes defaults, and provides examples. This adds significant meaning beyond the basic schema types.

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 'Duplicate all regions within a beat range to a new position.' It specifies the action (duplicate) and resource (regions within a beat range). The mention of 'arrangement operation producers use constantly' and examples differentiate it from other duplicate tools.

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?

Provides clear examples like 'copy verse 1 to bar 17' and explains when to use (copying sections). However, it does not explicitly state when not to use it versus alternatives like duplicate_region or move_section, leaving some ambiguity.

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