Skip to main content
Glama

list_markers

Retrieve all markers and regions from a REAPER project to organize and navigate audio editing sessions.

Instructions

List all markers and regions in the project.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The MCP tool registration and wrapper function for list_markers, which delegates the call to the ReaperAdapter.
    @mcp.tool()
    def list_markers() -> dict[str, Any]:
        """List all markers and regions in the project."""
        try:
            return _wrap(adapter.list_markers())
        except Exception as exc:
            return _err(exc)
  • The implementation of list_markers in ReaperAdapter, which directly calls the underlying BridgeClient to fetch marker data from REAPER.
    def list_markers(self) -> list[dict[str, Any]]:
        return self._client.call("list_markers")
Behavior3/5

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

No annotations provided, so description carries full burden. States 'all' implying unfiltered retrieval, but lacks disclosure on safety profile (though implied by 'List'), performance characteristics, or whether markers/regions are returned in a unified structure. Output schema exists per context signals, reducing some burden.

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?

Single sentence with zero redundancy. Front-loaded with action verb. 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?

Appropriate for tool complexity: 0 parameters with 100% schema coverage and existing output schema. Description adequately covers the dual scope (markers + regions) without needing to detail return values. Could benefit from noting the unfiltered nature explicitly.

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?

Input schema has zero properties. Per calibration rules, 0 params = baseline 4. Description appropriately does not fabricate parameters.

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?

Specific verb 'List' + clear resources 'markers and regions' + scope 'in the project'. Critically mentions 'regions' alongside markers, distinguishing it from sibling tools like add_marker or delete_marker that might handle only markers.

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 explicit guidance on when to use versus alternatives (e.g., vs get_project_info which might include marker data) or prerequisites. While the operation is straightforward, there is no 'when to use' or 'when not to use' instruction.

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