reaper-reapy-mcp

Overview Schema Source Related Servers Discussions Admin

delete_item

Remove any media item from a REAPER track. Provide the track index and item location (position index or internal ID) to target the exact clip for deletion.

Instructions

Delete a media item from a track.

Item Identification - Accepts BOTH types:

track_pos_idx (integer): Simple index like 0, 1, 2
direct_item_id (string): Internal ID like "MediaItem*0x..."

Args: track_index: Index of the track item: EITHER integer track_pos_idx OR string direct_item_id

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "track_index": "<track_index>",
      "item": "<item>"
    },
    "name": "delete_item"
  }
}

Input Schema

Name	Required	Description	Default
`item`	Yes
`track_index`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.4Aug 7, 2026

TDQS

A3.7/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It merely states the destructive action without elaborating on irreversibility, side effects on the project, or error handling, leaving significant gaps for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and front-loaded with the main purpose, followed by a focused, well-structured explanation of item identification. The minor redundancy between the bulleted list and the Args block does not detract significantly.

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?

For a simple delete tool with two parameters and an output schema, the description covers the essential invocation details. However, it lacks context about side effects, undo behavior, or when to prefer this tool over siblings, leaving it only minimally complete.

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?

The schema has no parameter descriptions (0% coverage), but the description fully compensates by explaining both parameters: track_index as the track's index, and item as either an integer track_pos_idx or a string direct_item_id, with concrete examples for each.

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 clearly states the tool's action with a specific verb and resource: 'Delete a media item from a track.' This distinguishes it from sibling deletion tools like delete_region and delete_marker, which target different resources.

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?

The description implies when to use the tool (when you need to delete a media item) and explains the two accepted item identification methods, but it does not explicitly mention alternatives or when not to use it, such as pointing to delete_region or delete_marker for other object types.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.