Skip to main content
Glama

get_all_tracks

Read-only

Retrieve information about every track in the current REAPER project, including each track's details and index, so you can inspect or manage the full track list.

Instructions

Get information about all tracks in the project, in get_track's shape plus index.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_all_tracks"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.7.3

TDQS

A3.7/5.0
Behavior3/5

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

readOnlyHint already declares this a safe read. The description adds one useful behavioral detail beyond annotations – the return shape mirrors get_track with an added index – but says nothing about ordering, empty-project behavior, or cost on large projects. Acceptable but thin given there is no output schema.

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?

A single front-loaded sentence of roughly fifteen words with no filler; the most important scoping fact ('all tracks') comes before the return-shape note.

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?

For a zero-parameter read tool with no output schema, the description covers what matters: scope, safe-read nature, and the shape of the returned objects via a reference to get_track. The cross-reference requires the agent to already know get_track's fields, which is a minor gap but reasonable in a large track-centric toolset.

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 tool takes zero parameters, so the baseline is 4; the schema has nothing for the description to compensate for, and no parameter confusion is possible.

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 a specific verb and resource ('Get information about all tracks in the project') and differentiates itself from the sibling get_track by scoping to ALL tracks and noting the extra index field. An agent can distinguish it from get_track, get_track_count and get_selected_tracks, though the distinction is implied rather than stated outright.

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?

Usage is only implied: 'all tracks' suggests using this instead of looping get_track, but the description never says when to choose this over get_track or get_selected_tracks. No exclusions or prerequisites are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools