Skip to main content
Glama

insert_audio_file

Add audio files to specific tracks at precise time positions in REAPER projects for audio editing and arrangement.

Instructions

Insert an audio file onto a track at the given position (seconds).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
track_indexYes
file_pathYes
positionYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the `insert_audio_file` tool, which is registered as an MCP tool and calls the adapter.
    @mcp.tool()
    def insert_audio_file(
        track_index: int,
        file_path: str,
        position: float,
    ) -> dict[str, Any]:
        """Insert an audio file onto a track at the given position (seconds)."""
        try:
            return _wrap(
                adapter.insert_audio_file(
                    track_index=track_index,
                    file_path=file_path,
                    position=position,
                )
            )
        except Exception as exc:
            return _err(exc)
  • The adapter method that facilitates the actual communication with the Reaper client to insert the audio file.
    def insert_audio_file(
        self,
        track_index: int,
        file_path: str,
        position: float,
    ) -> dict[str, Any]:
        return self._client.call(
            "insert_audio_file",
            track_index=track_index,
            file_path=file_path,
            position=position,
        )
Behavior2/5

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

With no annotations provided, the description carries the full burden of disclosure. While 'Insert' implies mutation, the description fails to clarify whether this overwrites existing content, creates a new media item, validates file existence, or specifies the return value structure (despite an output schema existing).

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?

Extremely concise at 11 words with zero redundancy. The sentence is front-loaded with the verb 'Insert' and immediately identifies the object and location parameters.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's mutative nature, 0% schema description coverage, and lack of annotations, the description is insufficient. It omits essential operational context like file format support, error handling behavior, and interaction with existing track content.

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?

The description adds the critical unit '(seconds)' for the position parameter and implicitly maps 'audio file' to file_path and 'track' to track_index. However, with 0% schema description coverage, it should specify whether paths must be absolute, if track_index is 0-based, and validation constraints.

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?

The description clearly states the action (insert), resource (audio file), and target location (track at given position in seconds). It effectively distinguishes from sibling tools like `create_midi_item` or `insert_midi_event` by specifying 'audio file' versus MIDI operations, though it does not explicitly name alternatives.

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?

The description provides no guidance on when to use this tool versus siblings like `duplicate_item`, `move_media_item`, or `create_midi_item`. It omits prerequisites (e.g., track must exist) and file format requirements.

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