Skip to main content
Glama
Sign In
Ableton MCP Extended

Ableton MCP Extended

by zabolotniydj
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_external_plugins

Search discovered VST/AU plugins by name, limit results, or force a rescan to find a specific external instrument or effect without browsing Ableton's browser manually.

Instructions

List discovered external plugins (VST/AU), optionally filtered by name query.

Parameters:

  • query: Optional case-insensitive search string.

  • max_results: Maximum number of plugins to display.

  • refresh_cache: If True, force a rescan instead of using cached results.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_external_plugins"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNo
max_resultsNo
refresh_cacheNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the transparency burden. It discloses case-insensitive search, result limiting, and the cache/refresh behavior. It does not elaborate on what 'discovered' means or potential side effects of forced rescans, but the core behavior is transparent enough.

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?

The description is concise and well-structured: a single purpose sentence followed by a compact parameter list. No filler or redundant information is present.

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

Completeness4/5

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

The output schema covers return-value structure, and the description covers purpose, filtering, result limiting, and cache behavior. The only notable gap is lack of guidance on when to select this tool over sibling browser/plugin tools, but for a simple list operation the description is largely complete.

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?

Schema description coverage is 0%, so the parameter descriptions in the tool description are essential. All three parameters are explained with meaningful semantics: query's case-insensitivity, max_results' display limit, and refresh_cache's forced rescan behavior.

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 discovered external plugins (VST/AU) with optional name filtering. This specific verb+resource+scope differentiates it from siblings like load_external_plugin and the browser-navigation tools.

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

Usage Guidelines3/5

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

The description implies this is for browsing/or discovering available plugins before loading one, but it does not explicitly state when to use it versus alternatives such as get_browser_tree or get_browser_items_at_path. There are no exclusions or comparison guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools