Skip to main content
Glama

create_track

Add a new track to REAPER projects with customizable name and position for audio and MIDI arrangement.

Instructions

Insert a new track.

  • name: track name (default "Track N")

  • index: 0-based position (default: append at end)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
indexNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The MCP tool handler function for 'create_track' in the server. It wraps the logic by calling the reaper_adapter.
    def create_track(name: str | None = None, index: int | None = None) -> dict[str, Any]:
        """
        Insert a new track.
        - name: track name (default "Track N")
        - index: 0-based position (default: append at end)
        """
        try:
            return _wrap(adapter.create_track(name=name, index=index))
        except Exception as exc:
            return _err(exc)
  • Registration of the create_track tool using the @mcp.tool() decorator.
    @mcp.tool()
    def create_track(name: str | None = None, index: int | None = None) -> dict[str, Any]:
  • The adapter function that interfaces with the REAPER client to execute the create_track action.
    def create_track(
        self,
        name: str | None = None,
        index: int | None = None,
    ) -> dict[str, Any]:
        return self._client.call("create_track", name=name, index=index)
Behavior3/5

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

No annotations provided, so description carries full burden. Adds valuable default behavior (auto-naming as 'Track N', appends to end if index omitted), but omits what the output contains (track ID? full track object?), error conditions, or side effects like auto-selection.

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

Conciseness4/5

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

Front-loaded purpose statement followed by efficient bullet parameter documentation. No redundant text, though bullet format blends parameter docs into main description rather than using schema descriptions.

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

Completeness3/5

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

Tool has only 2 parameters with simple types (string/null, integer/null) and output schema exists. Description covers input behavior adequately but could mention return value structure briefly given this is a creation operation where track identification matters.

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

Parameters4/5

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

Schema has 0% description coverage (titles only). Description compensates by documenting both parameters: name explains the 'Track N' default pattern, and index clarifies 0-based positioning and append behavior, adding necessary semantic context missing from schema.

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?

States specific action (Insert/create) and resource (track). Uses 'new' which implicitly distinguishes from sibling 'duplicate_track', though lacks explicit contrast with alternatives like using 'duplicate_track' on an empty track.

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?

No guidance provided on when to use versus alternatives (e.g., 'duplicate_track' for copying existing tracks), prerequisites (project must be open), or when to prefer default appending versus specific index insertion.

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