cut_selected_items
Move selected audio or MIDI items from a REAPER arrangement to the clipboard for pasting into another track or project.
Instructions
Cut selected items to clipboard.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Move selected audio or MIDI items from a REAPER arrangement to the clipboard for pasting into another track or project.
Cut selected items to clipboard.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.7.3Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It does not state that the source items are removed from the timeline, whether the operation is undoable, whether it depends on a time selection, or whether the clipboard survives project changes. 'Cut' implies removal but this is convention, not disclosure.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with zero filler; the verb and the affected resource come first. Nothing in it is redundant or restating the tool name mechanically.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter clipboard verb with no output schema and no annotations, a short description is largely sufficient. Still missing are the implicit-selection dependency and the removal side effect, which are the details an agent needs to chain this correctly with paste_items.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. It correctly signals that the target set is implicit (whatever is currently selected) rather than passed in.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (cut) and resource (selected items) with the destination (clipboard), so the action is unambiguous. It does not explicitly distinguish itself from near-neighbours like copy_selected_items or delete_selected_items, though 'cut' conventionally implies both copy and removal.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no when-to-use guidance, no stated alternative to copy_selected_items or delete_selected_items, and no prerequisite such as requiring a prior selection or routing to paste_items as the follow-up. The agent must infer all routing from the name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.