Skip to main content
Glama

script_list

List ReaScripts (.lua/.eel) in REAPER's Scripts folder, returning script paths and descriptions. Filter by case-insensitive path substring to narrow results.

Instructions

List ReaScripts (.lua/.eel only) found in REAPER's own Scripts folder.

Never scans anywhere else — this is hard-coded to REAPER's Scripts folder, not a caller-supplied path. Returns each script's path (relative to the Scripts folder — pass this straight to script_run) and description (parsed from an @description/@about header comment if present, empty string otherwise). Capped at 300 results; use filter (case-insensitive substring match against path only — not description) to narrow a larger install.

filter matches path, not description: description requires opening and reading the file, which only happens for scripts that already matched by path. Installs with large community script packs (a few thousand .lua files) would otherwise take minutes to filter. If you can't find a script by keyword, its path may not contain that keyword even though its description does — try a shorter/different substring or browse by folder instead.

Args: filter: Optional case-insensitive substring filter (matches path only).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filterNo
Behavior5/5

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

With no annotations, the description fully carries the behavioral burden. It discloses the hard-coded folder path, return format (path + parsed description), result cap, filter semantics (path-only, case-insensitive), performance rationale for not filtering by description, and a potential pitfall for keyword searches. This is exceptional transparency.

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 description is front-loaded with the core purpose and efficiently structured with an Args section. The second paragraph slightly repeats the 'filter matches path only' statement, adding some redundancy, but overall every sentence contributes meaningful detail.

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?

For a simple list tool with one optional parameter and no output schema, the description fully explains return values (relative path and description), limits (300 cap), and filter behavior. It leaves no significant gaps for an agent to select and invoke the tool correctly.

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

Parameters5/5

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

The schema only defines 'filter' with a default, but the description thoroughly explains its meaning: case-insensitive substring match against path only, not description, with reasoning and guidance on narrowing searches. This fully compensates for the 0% schema description coverage.

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?

The description clearly states the tool lists ReaScripts (.lua/.eel only) from REAPER's Scripts folder, with a specific verb and resource. It distinguishes itself from script_run by focusing on enumeration rather than execution, and is unambiguous about scope.

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?

The description gives practical usage context: reveals hard-coded scope, 300-result cap, filter usage, and explicitly points to passing the path to script_run. It does not name alternative tools or state when not to use it, but the unique purpose makes this less critical.

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/xDarkzx/Reaper-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server