Skip to main content
Glama

set_track_properties

Adjust track properties like volume, pan, mute, solo, and name in REAPER projects to customize audio mixing and arrangement.

Instructions

Modify one or more properties of a track.

  • volume: linear amplitude (1.0 = 0 dB)

  • pan: -1.0 (full left) to 1.0 (full right)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
track_indexYes
nameNo
volumeNo
panNo
muteNo
soloNo
armNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The MCP tool registration and handler implementation in server.py.
    def set_track_properties(
        track_index: int,
        name: str | None = None,
        volume: float | None = None,
        pan: float | None = None,
        mute: bool | None = None,
        solo: bool | None = None,
        arm: bool | None = None,
    ) -> dict[str, Any]:
        """
        Modify one or more properties of a track.
        - volume: linear amplitude (1.0 = 0 dB)
        - pan: -1.0 (full left) to 1.0 (full right)
        """
        try:
            return _wrap(
                adapter.set_track_properties(
                    track_index=track_index,
                    name=name,
                    volume=volume,
                    pan=pan,
                    mute=mute,
                    solo=solo,
                    arm=arm,
                )
            )
        except Exception as exc:
            return _err(exc)
  • The adapter helper method that forwards the call to the BridgeClient.
    def set_track_properties(
        self,
        track_index: int,
        name: str | None = None,
        volume: float | None = None,
        pan: float | None = None,
        mute: bool | None = None,
        solo: bool | None = None,
        arm: bool | None = None,
    ) -> dict[str, Any]:
        return self._client.call(
            "set_track_properties",
            track_index=track_index,
            name=name,
            volume=volume,
            pan=pan,
            mute=mute,
            solo=solo,
            arm=arm,
        )
Behavior3/5

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

Adds valuable unit context for volume (linear amplitude, 1.0 = 0 dB) and pan (-1.0 to 1.0) that the schema doesn't provide. However, missing critical behavioral details like mutation confirmation, atomicity (all-or-nothing updates), or validation rules for the required track_index parameter.

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

Conciseness3/5

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

The structure is logical (purpose first, then parameter specifics) and avoids redundancy, but the overall length is insufficient for a 7-parameter tool with zero schema coverage. The brevity becomes under-specification given the complexity.

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?

Inadequate for the tool's complexity. Despite having an output schema (relieving return-value documentation duties), the description fails to document 5 of 7 parameters and omits safety/validation context for a mutation operation.

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

Parameters2/5

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

With 0% schema description coverage, the description only compensates for 2 of 7 parameters (volume, pan). The required track_index and optional parameters (name, mute, solo, arm) receive no semantic explanation, leaving the majority of inputs undocumented.

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

Purpose3/5

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

States the basic action (Modify) and resource (track properties) clearly, but fails to differentiate from sibling tools like set_track_input or set_track_send that also modify track attributes. The scope of 'properties' is only partially illustrated through the volume/pan examples.

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?

Provides no guidance on when to use this tool versus alternatives (e.g., set_track_input, set_track_send) or prerequisites (e.g., track must exist). No mention of error conditions or partial update behavior.

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