Skip to main content
Glama

render_time_selection

Render a specific time range from a REAPER project to an audio file for playback or export.

Instructions

Render a time range to an audio file using REAPER's render pipeline.

  • output_path: absolute path including extension (e.g. '/tmp/mix.wav'). REAPER uses the current render format; set a .wav extension for PCM output.

  • start_time / end_time: seconds

  • sample_rate: 0 = use project rate

  • channels: 1=mono, 2=stereo Returns output_path and file_size_bytes so you can verify the file was written. After rendering, attach the file to this conversation so the audio can be heard.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
output_pathYes
start_timeYes
end_timeYes
sample_rateNo
channelsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The MCP tool handler function for `render_time_selection`, decorated with `@mcp.tool()` and utilizing `adapter.render_time_selection`.
    @mcp.tool()
    def render_time_selection(
        output_path: str,
        start_time: float,
        end_time: float,
        sample_rate: int = 0,
        channels: int = 2,
    ) -> dict[str, Any]:
        """
        Render a time range to an audio file using REAPER's render pipeline.
        - output_path: absolute path including extension (e.g. '/tmp/mix.wav').
          REAPER uses the current render format; set a .wav extension for PCM output.
        - start_time / end_time: seconds
        - sample_rate: 0 = use project rate
        - channels: 1=mono, 2=stereo
        Returns output_path and file_size_bytes so you can verify the file was written.
        After rendering, attach the file to this conversation so the audio can be heard.
        """
        try:
            return _wrap(
                adapter.render_time_selection(
                    output_path=output_path,
                    start_time=start_time,
                    end_time=end_time,
  • The adapter method that forwards the `render_time_selection` tool request to the REAPER client via `_client.call`.
    def render_time_selection(
        self,
        output_path: str,
        start_time: float,
        end_time: float,
        sample_rate: int = 0,
        channels: int = 2,
    ) -> dict[str, Any]:
        return self._client.call(
            "render_time_selection",
            output_path=output_path,
            start_time=start_time,
            end_time=end_time,
            sample_rate=sample_rate,
            channels=channels,
        )
Behavior4/5

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

No annotations provided, so description carries full burden. Explains REAPER's format handling ('uses current render format'), documents return values (output_path, file_size_bytes), and implies file system side effects. Could improve by mentioning overwrite behavior or resource requirements.

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?

Excellent structure: single-sentence purpose upfront followed by bullet-point parameter documentation, return value disclosure, and post-action guidance. No wasted words; every sentence earns its place despite explaining 5 undocumented parameters.

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

Completeness5/5

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

Complete for a medium-complexity file I/O tool. Despite bare schema, all 5 parameters are documented. Acknowledges return values (output_path, file_size_bytes) and includes practical workflow instruction for the conversation context.

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?

Schema has 0% description coverage, but description fully compensates: output_path includes format example and extension guidance; start_time/end_time specify units (seconds); sample_rate explains special value 0; channels maps integers to mono/stereo semantics.

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?

Clear specific verb 'Render', resource 'time range to an audio file', and scope 'using REAPER's render pipeline'. Distinguished from sibling insert_audio_file (importing existing files) and analysis tools.

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?

Provides post-render workflow guidance ('attach the file to this conversation'), but lacks explicit when-to-use vs alternatives like insert_audio_file or when to choose rendering over other export methods.

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