Skip to main content
Glama

mcp_opendaw_reorder_sections

Rearrange song sections by providing a new order of beat ranges. Notes are moved to restructure the timeline, enabling full song form editing.

Instructions

Reorder song sections — rearrange blocks on the timeline.

Takes a list of section boundaries and rearranges them into a new order. Each section is defined by its start and end beat. The tool collects all note content from each section, then places them in the specified new order, back-to-back, starting from the first section's original start position.

This is the full song structure editor: instead of swapping two sections (swap_sections), you can completely rearrange the form. Turn verse-chorus-verse-chorus-bridge-chorus into chorus-verse-bridge-chorus-verse-chorus in one call.

section_order: JSON array of section objects, each with "start" and "end" beat positions, listed in the NEW desired order. Example: '[{"start":0,"end":8},{"start":16,"end":24},{"start":8,"end":16}]' This takes sections at [0-8], [16-24], [8-16] and places them in that order, starting at beat 0.

Sections can overlap in the original but not in the output — they are placed sequentially. Section lengths are preserved.

unit_indices: Comma-separated unit indices to process ("" = all units).

Returns sections reordered, notes moved per unit, new section layout.

Example:

Move chorus to front

reorder_sections('[{"start":16,"end":32},{"start":0,"end":8},{"start":8,"end":16}]')

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
unit_indicesNo
section_orderYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

The description details how sections are collected, placed sequentially, and that lengths are preserved. No annotations provided, so the description bears full burden and does it well.

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 summary, explanation, contrast, parameter details, and example, though slightly lengthy.

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?

Covers parameters, return values, and example; missing error conditions or project impact details, but adequate given output schema exists.

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?

With 0% schema coverage, the description fully explains both parameters: section_order as a JSON array with start/end beats and example, unit_indices as comma-separated indices or empty for all.

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 'Reorder song sections — rearrange blocks on the timeline' and contrasts with swap_sections, making it distinct among siblings.

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?

It explains when to use this tool vs swap_sections with an explicit example, but does not cover all alternatives or when not to use it.

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