Skip to main content
Glama

get_track_items

Lists media items on a specified track, showing position, length, and take details for project organization in REAPER.

Instructions

List all media items on a track with their position, length, and take info.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
track_indexYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool registration and handler for get_track_items.
    def get_track_items(track_index: int) -> dict[str, Any]:
        """List all media items on a track with their position, length, and take info."""
        try:
            return _wrap(adapter.get_track_items(track_index=track_index))
        except Exception as exc:
            return _err(exc)
  • Adapter method in ReaperAdapter class that dispatches the call to the BridgeClient.
    def get_track_items(self, track_index: int) -> dict[str, Any]:
        return self._client.call("get_track_items", track_index=track_index)
Behavior3/5

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

With no annotations provided, the description carries the full burden. It partially compensates by previewing the output fields (position, length, take info), but fails to disclose safety characteristics, error conditions (e.g., invalid track_index), or performance characteristics for tracks with many items.

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 single 12-word sentence is efficiently front-loaded with the action verb 'List' and contains no redundancy. Every word contributes to understanding the scope (media items), location (track), and output characteristics.

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 a single parameter and an output schema (per context signals), the description is sufficiently complete. It appropriately previews key output fields without replicating the full schema, though it could benefit from noting the REAPER-specific 'take' terminology.

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

Parameters3/5

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

Schema description coverage is 0%, requiring the description to compensate. It provides minimal semantic context by mentioning 'on a track,' which clarifies that 'track_index' identifies the container track for the query, but offers no further details on constraints, indexing (0 vs 1-based), or valid ranges.

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?

The description uses the specific verb 'List' with the resource 'media items on a track' and details the output content (position, length, take info). It effectively distinguishes from sibling 'get_item_properties' (which implies retrieving properties of a single specified item) by emphasizing the bulk listing nature and specific data returned.

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?

The description provides implied context that this tool is used to enumerate media items on a specific track, but offers no explicit guidance on when to use this versus 'get_item_properties' for single-item lookups, or prerequisites like track existence.

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