Skip to main content
Glama
danielkinahan

ReaMCP

by danielkinahan
OverviewSchemaRelated ServersScoreDiscussions
Local

duplicate_time_range

Copy and paste audio or MIDI items within a specified time range to repeat sections in REAPER projects. Use this tool to extend song forms by duplicating choruses, verses, or outros multiple times.

Instructions

Copy all items overlapping [start_time, end_time) and paste them immediately after end_time, repeating repeat_count times. Useful for extending song form (repeating a chorus, creating an outro).

  • start_time / end_time: seconds

  • repeat_count: how many copies to paste (default 1) Returns the new project end time after pasting.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
start_timeYes
end_timeYes
repeat_countNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/reaper_mcp/server.py:886-908 (handler)
    The tool 'duplicate_time_range' is registered as an MCP tool and calls the adapter method.
    def duplicate_time_range(
    start_time: float,
    end_time: float,
    repeat_count: int = 1,
) -> dict[str, Any]:
    """
    Copy all items overlapping [start_time, end_time) and paste them immediately
    after end_time, repeating repeat_count times. Useful for extending song form
    (repeating a chorus, creating an outro).
    - start_time / end_time: seconds
    - repeat_count: how many copies to paste (default 1)
    Returns the new project end time after pasting.
    """
    try:
        return _wrap(
            adapter.duplicate_time_range(
                start_time=start_time,
                end_time=end_time,
                repeat_count=repeat_count,
            )
        )
    except Exception as exc:
        return _err(exc)
  • src/reaper_mcp/reaper_adapter.py:339-350 (helper)
    The adapter method 'duplicate_time_range' that makes the call to the underlying BridgeClient.
    def duplicate_time_range(
    self,
    start_time: float,
    end_time: float,
    repeat_count: int = 1,
) -> dict[str, Any]:
    return self._client.call(
        "duplicate_time_range",
        start_time=start_time,
        end_time=end_time,
        repeat_count=repeat_count,
    )

Tool Definition Quality

A4.5/5.0
Behavior4/5

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

With no annotations provided, description carries full behavioral burden effectively. It specifies exact mechanics (overlapping items detection, insertion point 'immediately after end_time'), units (seconds), and return value ('new project end time'). Could enhance further by noting that existing content after end_time is shifted to accommodate pasted material.

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?

Perfectly structured: front-loaded operational sentence followed by use-case context, then targeted parameter annotations. No redundancy; every phrase adds value beyond the schema. Bullet format for parameters aids scanability.

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?

Comprehensive coverage for a 3-parameter mutation tool. Acknowledges output schema existence by documenting return value. Musical domain context (chorus/outro) enriches completeness. Minor gap: doesn't clarify if operation is atomic or handles edge cases (zero items selected).

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?

Excellent compensation for 0% schema description coverage. Provides units for temporal parameters ('seconds'), clarifies the inclusive-exclusive nature of the time range '[start_time, end_time)', and explains repeat_count semantics ('how many copies') plus its default value (1). Adds essential meaning entirely absent from schema.

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?

Description opens with specific action 'Copy all items overlapping... and paste them immediately after end_time' clearly identifying the verb (copy/paste), resource (time range with overlapping items), and scope. Distinguishes from siblings like duplicate_item and duplicate_track by specifying time-range-based operation vs single-item or track-based duplication.

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 contextual guidance with 'Useful for extending song form (repeating a chorus, creating an outro)' helping agents recognize musical use cases. While it doesn't explicitly name alternative duplication tools, the specific resource description (items overlapping a time range) clearly delineates appropriate selection criteria.

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