Skip to main content
Glama
danielkinahan

ReaMCP

by danielkinahan
OverviewSchemaRelated ServersScoreDiscussions
Local

delete_marker

Remove markers or regions from REAPER projects using their index position to manage project structure and navigation points.

Instructions

Delete a marker or region by its 0-based enumeration index (from list_markers).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
enum_indexYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/reaper_mcp/server.py:823-831 (handler)
    MCP tool registration and handler for 'delete_marker'.
    @mcp.tool()
def delete_marker(enum_index: int) -> dict[str, Any]:
    """
    Delete a marker or region by its 0-based enumeration index (from list_markers).
    """
    try:
        return _wrap(adapter.delete_marker(enum_index=enum_index))
    except Exception as exc:
        return _err(exc)
  • src/reaper_mcp/reaper_adapter.py:456-457 (helper)
    Adapter method that translates the tool call to the underlying BridgeClient.
    def delete_marker(self, enum_index: int) -> dict[str, Any]:
    return self._client.call("delete_marker", enum_index=enum_index)

Tool Definition Quality

A3.5/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. While 'Delete' implies destruction, lacks crucial behavioral details for a destructive operation: whether deletion is permanent, if it shifts indices of subsequent markers, error behavior on invalid index, or side effects.

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 waste. Front-loaded with the action verb, immediately followed by the resource and parameter explanation. 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 a single-parameter destructive tool. The critical dependency on list_markers is documented. Since an output schema exists (per context signals), the description doesn't need to explain return values. Could mention error cases for completeness.

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?

Schema coverage is 0% (no property descriptions), but the description compensates effectively by explaining 'enum_index' is '0-based' and sourced from list_markers, adding critical semantic context missing from the schema title alone.

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?

Clear verb ('Delete') and resource ('marker or region'). Distinguishes from sibling delete operations (delete_track, delete_media_item) by specifying the target resource. Referencing 'list_markers' clarifies the data source.

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?

Implies workflow dependency by stating the index comes 'from list_markers', hinting that tool should be called after listing. However, lacks explicit 'when to use vs alternatives' guidance or prerequisites (e.g., project must be open).

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