Skip to main content
Glama

remove_track_send

Remove a send from a track in REAPER by specifying the track and send index to manage audio routing and project organization.

Instructions

Remove a send from a track by its 0-based send index.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
track_indexYes
send_indexYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The MCP tool handler for "remove_track_send", which wraps the adapter call.
    @mcp.tool()
    def remove_track_send(track_index: int, send_index: int) -> dict[str, Any]:
        """Remove a send from a track by its 0-based send index."""
        try:
            return _wrap(
                adapter.remove_track_send(track_index=track_index, send_index=send_index)
            )
        except Exception as exc:
            return _err(exc)
  • The adapter method that communicates with the Reaper client to remove a track send.
    def remove_track_send(
        self, track_index: int, send_index: int
    ) -> dict[str, Any]:
        return self._client.call(
            "remove_track_send",
            track_index=track_index,
            send_index=send_index,
        )
Behavior2/5

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

No annotations provided, so description carries full burden. States 'Remove' implying destruction but fails to disclose side effects (e.g., whether connected receives are affected), reversibility, or what the output schema contains. No mention of failure modes for invalid indices.

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, 9 words. Action-fronted with zero redundancy. Every word serves the core definition.

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?

Minimally adequate for a 2-parameter destructive operation. Given zero schema descriptions and no annotations, it should explicitly document both parameters' semantics and valid ranges. The existence of an output schema mitigates the need for return value description.

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 coverage is 0%, requiring description compensation. It clarifies 'send_index' is '0-based' and implies 'track_index' via 'from a track'. However, it lacks explicit confirmation that track_index is also 0-based (implied but not stated) and omits valid ranges or formats for both parameters.

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 'Remove' targeting resource 'send' from 'track'. Explicitly mentions '0-based send index' which distinguishes the indexing scheme. However, it does not explicitly differentiate from sibling tool 'set_track_send' (which modifies vs removes).

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 indexing hint ('0-based') but lacks explicit prerequisites (e.g., track must exist, send must exist at index), error conditions, or guidance on when to use 'remove' versus 'set_track_send' (disable) or 'create_track_send'.

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