Skip to main content
Glama

add_marker

Add markers or regions to REAPER projects to mark specific time positions or define sections for audio editing and organization.

Instructions

Add a marker or region to the project.

  • position: time in seconds

  • is_region: True to create a region; also requires region_end

  • region_end: end time in seconds (only for regions)

  • color: REAPER color integer (0 = default)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
positionYes
nameNo
is_regionNo
region_endNo
colorNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The implementation of the add_marker logic in the adapter class, which calls the bridge client.
    def add_marker(
        self,
        position: float,
        name: str = "",
        is_region: bool = False,
        region_end: float | None = None,
        color: int = 0,
    ) -> dict[str, Any]:
        return self._client.call(
            "add_marker",
            position=position,
            name=name,
            is_region=is_region,
            region_end=region_end,
            color=color,
        )
  • The MCP tool registration and wrapper for the add_marker tool.
    def add_marker(
        position: float,
        name: str = "",
        is_region: bool = False,
        region_end: float | None = None,
        color: int = 0,
    ) -> dict[str, Any]:
        """
        Add a marker or region to the project.
        - position: time in seconds
        - is_region: True to create a region; also requires region_end
        - region_end: end time in seconds (only for regions)
        - color: REAPER color integer (0 = default)
        """
        try:
            return _wrap(
                adapter.add_marker(
                    position=position,
                    name=name,
                    is_region=is_region,
                    region_end=region_end,
                    color=color,
                )
            )
        except Exception as exc:
            return _err(exc)
Behavior3/5

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

No annotations provided, so description carries full disclosure burden. Adds valuable domain context ('REAPER color integer') and业务 logic constraints (region_end requirement). However, lacks disclosure of failure modes, side effects, or persistence guarantees.

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?

Structure is efficient: single-sentence purpose followed by bulleted parameter semantics. No wasted words; every line conveys necessary constraint information. Appropriate length for the parameter count.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 0% schema coverage and no annotations, the description adequately covers most parameters but has a notable gap with the undocumented 'name' parameter. Presence of output_schema satisfies output documentation needs.

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?

With 0% schema description coverage, the description successfully compensates for 4 of 5 parameters, explaining units (seconds), conditional requirements, and domain-specific values (REAPER color). Only misses explaining the 'name' parameter's purpose.

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 specific action ('Add') and resources ('marker or region') clearly. Implies domain context (REAPER) via the color parameter description. Distinguishes from sibling delete_marker and list_markers by action verb, though doesn't explicitly reference them.

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?

Explains conditional logic between is_region and region_end ('also requires'), guiding when to use region_end. However, lacks explicit when-not-to-use guidance or comparison to sibling tools like list_markers for retrieval.

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