Skip to main content
Glama
danielkinahan

ReaMCP

by danielkinahan
OverviewSchemaRelated ServersScoreDiscussions
Local

delete_media_item

Remove a media item from a specified track in REAPER projects by providing track and item indices.

Instructions

Delete a media item from a track.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
track_indexYes
item_indexYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/reaper_mcp/server.py:190-197 (handler)
    The MCP tool registration and handler wrapper for `delete_media_item`. It catches exceptions and formats the result.
    def delete_media_item(track_index: int, item_index: int) -> dict[str, Any]:
    """Delete a media item from a track."""
    try:
        return _wrap(
            adapter.delete_media_item(track_index=track_index, item_index=item_index)
        )
    except Exception as exc:
        return _err(exc)
  • src/reaper_mcp/reaper_adapter.py:99-106 (handler)
    The implementation of `delete_media_item` in `ReaperAdapter`, which forwards the call to the `BridgeClient`.
    def delete_media_item(
    self, track_index: int, item_index: int
) -> dict[str, Any]:
    return self._client.call(
        "delete_media_item",
        track_index=track_index,
        item_index=item_index,
    )

Tool Definition Quality

C2.6/5.0
Behavior2/5

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

With zero annotations, the description bears full responsibility for behavioral disclosure. It fails to specify whether the underlying media file is deleted or merely removed from the track, whether the operation is undoable, or what the output schema contains. 'Delete' implies destruction but remains ambiguous about scope.

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

Conciseness3/5

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

Extremely concise (6 words) with no structural issues, but undersized given the lack of schema documentation and annotations. Front-loaded with the action, yet sacrifices necessary context for brevity.

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

Completeness2/5

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

Inadequate for a tool with zero schema descriptions and no annotations. While an output schema exists (reducing some burden), the description fails to explain critical DAW-specific semantics like index numbering schemes or destructive behavior scope, leaving significant operational gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 0% description coverage (only titles 'Track Index' and 'Item Index'). The description adds no semantic context: it does not clarify if indices are 0-based or 1-based, valid ranges, or the hierarchical relationship (whether item_index is track-relative or global).

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 (media item from a track). Effectively distinguishes from siblings like delete_track, delete_marker, and delete_midi_note by specifying 'media item' scope. Lacks explicit scope boundaries (e.g., removes from timeline vs. deletes source file).

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 no guidance on when to use versus alternatives like delete_track (when user wants to remove the track entirely) or move_media_item (when repositioning is preferred). No mention of prerequisites or index sourcing.

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