Skip to main content
Glama

move_media_item

Move a media item to a new timeline position in seconds within REAPER projects by specifying track index, item index, and position.

Instructions

Move a media item to a new timeline position (seconds).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
track_indexYes
item_indexYes
positionYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Registration and MCP tool handler for 'move_media_item'. It wraps the adapter's call.
    @mcp.tool()
    def move_media_item(
        track_index: int,
        item_index: int,
        position: float,
    ) -> dict[str, Any]:
        """Move a media item to a new timeline position (seconds)."""
        try:
            return _wrap(
                adapter.move_media_item(
                    track_index=track_index, item_index=item_index, position=position
                )
            )
        except Exception as exc:
            return _err(exc)
  • ReaperAdapter method that facilitates the bridge call to move a media item.
    def move_media_item(
        self, track_index: int, item_index: int, position: float
    ) -> dict[str, Any]:
        return self._client.call(
            "move_media_item",
            track_index=track_index,
            item_index=item_index,
            position=position,
        )
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. While 'Move' implies a mutation, the description lacks critical behavioral details: error handling for invalid indices, whether the move respects snap/grid settings, if overlapping items are allowed, or whether the operation is undoable (relevant given the 'undo' sibling 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 single sentence is front-loaded with the verb and contains no wasted words. However, given the 0% schema coverage and mutation behavior, the description is likely too concise rather than appropriately sized.

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?

For a mutation tool requiring specific integer indices to locate target objects, the description is insufficient. It fails to explain the addressing scheme (how tracks and items are indexed) or reference the output schema's return value, leaving significant gaps despite the existence of an output schema.

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 coverage is 0%, requiring the description to compensate. It only partially succeeds: '(seconds)' adds crucial unit semantics for the 'position' parameter, but 'track_index' and 'item_index' are completely undocumented, leaving users without guidance on how to obtain or format these required identifiers.

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?

The description uses a specific verb ('Move') and resource ('media item') and clarifies the positioning unit ('seconds'). It implicitly distinguishes from siblings like 'resize_media_item' and 'duplicate_item', though it could explicitly state this operates on existing items versus creating new ones.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., 'nudge_midi_notes' or 'resize_media_item'), nor does it mention prerequisites like obtaining valid track_index and item_index values from 'get_track_items' before invocation.

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