Skip to main content
Glama
xDarkzx

ReaperMCP

by xDarkzx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

marker_get_all

Retrieve all markers and regions from a REAPER project, with an optional cap to avoid context overload. Prefer project_get_overview for a lightweight summary.

Instructions

Get all markers and regions. For just the region list plus a cheap project overview, prefer project_get_overview() instead.

Args: max_results: Cap on returned markers/regions (default 500, hard ceiling 5000, prevents context blow-up on a marker-heavy project). truncated in the response says whether more exist.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
max_resultsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.7.1
    • addedInput schema / properties / max_results
      Added value: +{
+  "default": 500,
+  "title": "Max Results",
+  "type": "integer"
+}
  2. First observedv0.3.0

TDQS

A4.7/5.0
Behavior4/5

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

With no annotations provided, the description carries the behavioral burden and does it well: it discloses the max_results cap (500 default, 5000 ceiling), the rationale to prevent context blow-up, and the 'truncated' response flag that indicates more results exist. It stops short of explicitly confirming read-only behavior or describing the full response structure, but the 'get' semantics and truncation notes cover the main risks.

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?

Two tight paragraphs with no filler: the first sentence states the scope and sibling alternative, the second paragraph explains the only parameter and its caveats. Every sentence adds information an agent needs.

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?

The tool has a single optional parameter and no output schema, and the description explains both the parameter's behavior and the presence of a truncation flag. It is largely complete for correct invocation; the only noteworthy gap is that the overall return shape of markers/regions is not described, which is a minor omission for a simple retrieval tool with no annotations.

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

Parameters5/5

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

Schema description coverage is 0%, and the description fully compensates by explaining max_results with its default, hard ceiling, and effect on the response via 'truncated'. This gives an agent concrete guidance on why and how to set the optional parameter.

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 opens with 'Get all markers and regions', a specific verb plus resource, and immediately differentiates itself from project_get_overview by naming the alternative for a lighter subset. An agent can choose this tool over its siblings without inspecting schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly states when to prefer an alternative: 'For just the region list plus a cheap project overview, prefer project_get_overview() instead.' This directly addresses selection between related tools and leaves no ambiguity about the intended heavier use case.

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