Skip to main content
Glama

list_tracks

Retrieve a complete list of all tracks in your REAPER project with volume, pan, mute, solo, and arm state details for project management.

Instructions

List every track in the project with volume, pan, mute, solo, arm state.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The MCP tool handler for "list_tracks" which wraps the adapter call.
    @mcp.tool()
    def list_tracks() -> dict[str, Any]:
        """List every track in the project with volume, pan, mute, solo, arm state."""
        try:
            return _wrap(adapter.list_tracks())
        except Exception as exc:
            return _err(exc)
  • The Reaper adapter implementation that performs the RPC call to the Reaper client.
    def list_tracks(self) -> list[dict[str, Any]]:
        return self._client.call("list_tracks")
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It adds valuable context by enumerating the specific track states returned (volume, pan, mute, solo, arm), which supplements the output schema. However, it omits safety/profile information (e.g., read-only nature, performance characteristics).

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?

The description is a single sentence, front-loaded with the action ('List'), and efficiently enumerates the returned track properties without waste. Every word earns its place.

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?

Given the tool has no parameters and an output schema exists, the description appropriately focuses on enumerating the key return fields (volume, pan, etc.) rather than redundant return value documentation. It could improve by explicitly contrasting with 'get_track', but is sufficient for the tool's simplicity.

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?

The input schema contains zero parameters. Per the rubric, 0 parameters warrants a baseline score of 4, as there are no parameter semantics to describe beyond what the empty schema already communicates.

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?

The description uses the specific verb 'List' with the clear scope 'every track in the project.' It effectively distinguishes itself from the singular sibling 'get_track' by emphasizing 'every' (comprehensive listing vs. individual retrieval).

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?

The phrase 'List every track' provides implied contrast to 'get_track' (singular), suggesting this is for bulk retrieval. However, there is no explicit guidance on when to prefer this over 'get_track' or other track-related tools, nor are prerequisites mentioned.

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