Skip to main content
Glama
danielkinahan

ReaMCP

by danielkinahan
OverviewSchemaRelated ServersScoreDiscussions
Local

duplicate_track

Duplicate a track in REAPER projects by inserting an exact copy immediately after the original track. Use this tool to quickly replicate track configurations, effects, and settings for parallel processing or layered arrangements.

Instructions

Duplicate a track, inserting the copy immediately after the original.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
track_indexYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/reaper_mcp/server.py:214-220 (handler)
    The tool handler for "duplicate_track" defined in the MCP server.
    @mcp.tool()
def duplicate_track(track_index: int) -> dict[str, Any]:
    """Duplicate a track, inserting the copy immediately after the original."""
    try:
        return _wrap(adapter.duplicate_track(track_index=track_index))
    except Exception as exc:
        return _err(exc)
  • src/reaper_mcp/server.py:214-214 (registration)
    Registration of the "duplicate_track" tool using the FastMCP decorator.
    @mcp.tool()
  • src/reaper_mcp/reaper_adapter.py:120-121 (helper)
    The adapter method that forwards the "duplicate_track" call to the BridgeClient.
    def duplicate_track(self, track_index: int) -> dict[str, Any]:
    return self._client.call("duplicate_track", track_index=track_index)

Tool Definition Quality

A4/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. Discloses critical behavioral detail: insertion occurs 'immediately after the original.' However, omits whether track properties (FX, sends, envelopes) are duplicated or if the new track becomes selected.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single 10-word sentence with zero waste. Front-loaded action (Duplicate), followed by resource, then behavioral qualifier (insertion position)—every clause earns its place.

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?

Appropriate for a single-parameter mutation tool. Output schema exists (noted in context), absolving description from detailing return values. Could mention copied properties but covers core insertion behavior.

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

Parameters3/5

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

Schema coverage is 0% with no property descriptions. Description mentions 'a track' implying the target but does not explicitly map to track_index parameter or clarify indexing scheme (0-based vs 1-based). Single parameter has clear name, preventing lower score.

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?

Specific verb 'Duplicate' paired with resource 'track' and distinguished from siblings by 'inserting the copy immediately after the original'—clearly differentiates from create_track (new empty track) and duplicate_item (media items vs tracks).

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

Usage Guidelines3/5

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

Implies usage through the word 'duplicate' (copy existing vs create new) and clarifies positioning behavior, but lacks explicit when-to-use guidance or references to siblings like create_track or duplicate_time_range.

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/danielkinahan/ReaMCP'

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