Skip to main content
Glama
Sign In
reaper-mcp

reaper-mcp

by TwelveTake-Studios
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

move_tracks

Move specified tracks, preserving order, to a target index, optionally into the folder above the destination; folders move with their children.

Instructions

Move tracks, in their current order, to just above before_index. A folder moves with its children.

Args: before_index: Counted before the move; the track count moves them to the end. into_folder: Make them children of the track above the destination.

Returns: tracks: [{from, to}], each listed track's index before and after.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "track_indices": "<track_indices>",
      "before_index": "<before_index>"
    },
    "name": "move_tracks"
  }
}

Input Schema

NameRequiredDescriptionDefault
into_folderNo
before_indexYes
track_indicesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.10.1

TDQS

B3.3/5.0
Behavior3/5

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

destructiveHint=false is the only annotation, and the description supports it by explaining the cascade ('A folder moves with its children') and the out-of-range behaviour ('the track count moves them to the end'), which is real context beyond the annotations. It does not cover reversibility/undo, permission requirements, or whether child tracks are individually re-indexed.

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?

Front-loads the operation and destination rule, then the two parameter notes and the return shape; nothing is filler. The docstring-style 'Args:'/'Returns:' headers add mild noise, and the before_index sentence is awkwardly phrased.

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?

With no output schema the description usefully documents the return as [{from, to}] pairs, and it covers mutation and folder semantics. However, for an index-based move it omits the indexing base, behaviour when before_index is 0 or when into_folder targets the top of the project, and whether duplicate or non-contiguous indices are accepted.

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 the description carries the load and does document before_index (counted pre-move, clamped to end) and into_folder (nest under the track above the destination). It leaves track_indices' indexing base (0- vs 1-based) and duplicate-index handling unspecified, which is a meaningful gap for an index-based mutator.

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

Purpose4/5

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

States a specific verb+resource ('Move tracks') plus the destination semantics ('just above before_index', preserving current order) and the folder-cascade rule. It is clearly distinguishable from sibling mutators like insert_track or delete_track, though it never names a sibling it could be confused with.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use / when-not guidance, no mention of how track_indices relate to the selected-tracks siblings (select_track, get_selected_tracks), and no statement about undo. The agent must infer usage purely from the name and the move semantics.

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

Deploy Server

Other Tools