Skip to main content
Glama

delete_track

Remove a track from a REAPER project by specifying its index. This action is permanent and cannot be undone through REAPER's standard undo system.

Instructions

Delete a track by 0-based index. This is permanent and undoable via REAPER's undo system.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
track_indexYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The MCP tool definition and handler for delete_track.
    @mcp.tool()
    def delete_track(track_index: int) -> dict[str, Any]:
        """Delete a track by 0-based index. This is permanent and undoable via REAPER's undo system."""
        try:
            return _wrap(adapter.delete_track(track_index=track_index))
        except Exception as exc:
            return _err(exc)
  • The adapter method that forwards the call to the underlying bridge client.
    def delete_track(self, track_index: int) -> dict[str, Any]:
        return self._client.call("delete_track", track_index=track_index)
Behavior4/5

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

With no annotations provided, description carries full burden and effectively discloses critical safety info: operation is permanent but reversible via REAPER's undo system. Could improve by mentioning side effects (e.g., whether media items are deleted or moved to root).

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 sentences, zero waste. Front-loaded with action, second sentence delivers essential safety warning. Efficient structure.

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. Covers action, indexing scheme, and safety profile. Has output schema so return values need less explanation. Could mention validation behavior (invalid index handling) but adequate as-is.

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?

Compensates effectively for 0% schema description coverage by specifying '0-based index'—critical semantics for API correctness that the schema title 'Track Index' omits. Single parameter is well-documented given schema constraints.

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?

Clear specific verb ('Delete') + resource ('track') + scope ('by 0-based index'). Distinguishes clearly from sibling operations like create_track, duplicate_track, or remove_track_send.

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 caution via 'permanent' warning but lacks explicit when-to-use guidance or alternatives (e.g., mute vs delete, or what happens to media items on the track). No contrast with similar deletion tools like delete_media_item or delete_marker.

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