Eliminate unwanted FX plugins from REAPER tracks by specifying the track and FX index. Maintain an organized mixing environment with targeted removal.
Remove an FX plugin from a track by its index.
| Name | Required | Description | Default |
|---|---|---|---|
| fx_index | Yes | ||
| track_index | Yes |
Changes observed during successful MCP inspections.
v0.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so the description carries full burden. It only states the action without disclosing side effects (e.g., immediate removal, undo behavior, error handling for invalid indices).
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?
Single sentence with no wasted words. Front-loaded with the action and target.
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?
Essential context is missing: no mention of prerequisite steps (e.g., list_track_fx to get indices), no description of expected behavior for edge cases (e.g., invalid index), and no output schema to describe the result.
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?
Schema coverage is 0% and the description does not explain the parameters. 'track_index' and 'fx_index' are just named; their meaning (e.g., fx_index is the index in the track's FX chain) is not elaborated, leaving the agent to infer.
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?
The description clearly states the verb 'remove', the resource 'FX plugin', and the scope 'from a track by its index'. It distinguishes itself from sibling tools like add_fx and bypass_fx.
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?
No guidance on when to use this tool vs alternatives (e.g., bypass_fx). No prerequisites mentioned, such as needing to list track FX first to obtain the correct index.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.