Skip to main content
Glama

list_fx_presets

Retrieve available presets for an existing track effect, including factory presets and saved preset files, to streamline audio effect management in REAPER.

Instructions

List available presets for an FX already on a track. Returns two lists:

  • factory_presets: presets exposed by the plugin itself (CLAP, VST3, VST2 banks). Each entry has {index, name, source='factory'}. These can be loaded by name with set_fx_preset().

  • file_presets: .ffp/.fxp files found on disk under standard vendor preset dirs. Each entry has {name, category, path, source='file'}. Load via the 'path' field.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
track_indexYes
fx_indexYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The tool handler for 'list_fx_presets' which is registered with FastMCP.
    @mcp.tool()
    def list_fx_presets(
        track_index: int, fx_index: int
    ) -> dict[str, Any]:
        """
        List available presets for an FX already on a track.
        Returns two lists:
        - factory_presets: presets exposed by the plugin itself (CLAP, VST3, VST2 banks).
          Each entry has {index, name, source='factory'}. These can be loaded by name
          with set_fx_preset().
        - file_presets: .ffp/.fxp files found on disk under standard vendor preset dirs.
          Each entry has {name, category, path, source='file'}. Load via the 'path' field.
        """
        try:
            return _wrap(adapter.list_fx_presets(track_index=track_index, fx_index=fx_index))
        except Exception as exc:
            return _err(exc)
  • The underlying adapter method that calls the bridge client to list FX presets in REAPER.
    def list_fx_presets(
        self, track_index: int, fx_index: int
    ) -> dict[str, Any]:
        return self._client.call(
            "list_fx_presets",
            track_index=track_index,
            fx_index=fx_index,
        )
Behavior4/5

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

No annotations provided, so description carries full burden. Excellently discloses return structure—distinguishes factory_presets (CLAP/VST banks with indices) from file_presets (.ffp/.fxp files with paths). Explains the semantic differences between the two list types and their usage patterns. Could mention read-only/safety nature.

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

Conciseness5/5

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

Efficiently structured with clear header sentence followed byOutput format details using dashed list items. Every sentence serves a purpose. No wasted words. Front-loaded with the core action.

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

Completeness5/5

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

Rich explanation of output schema semantics (factory vs file distinction, source fields, loading mechanisms). Given output schema exists, description appropriately focuses on how to interpret and act on the returned data rather than repeating structural syntax. Links well to sibling set_fx_preset tool.

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). Description fails to compensate—it does not mention track_index or fx_index parameters at all, though they are somewhat inferable from the phrase 'FX already on a track'. With zero coverage, the description should explicitly document these required identifiers.

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?

Clear specific verb ('List') + resource ('presets') + scope ('for an FX already on a track'). Effectively distinguishes from sibling tools like list_available_fx (plugins vs presets) and set_fx_preset (loading vs listing).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides clear workflow context by explaining how to use the returned data (load factory presets by name with set_fx_preset, file presets via path field). States prerequisite that FX must already be on a track. Lacks explicit 'when not to use' or alternative approaches (e.g., manual parameter setting).

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