Search the Ableton Live 12 Browser by keyword and optional category to find instruments, effects, presets, samples, packs, and plug-ins.
Searches the Ableton Live 12 Browser for instruments, effects, presets, samples, packs, and plug-ins.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Search keyword or device name (e.g. 'Drift', 'Wavetable', 'Reverb'). | |
| category | No | Optional category filter. | all |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the behavioral burden. 'Searches' implies a safe read operation, but nothing is said about result format, result count, ordering, or pagination behavior, leaving real gaps for an agent relying on the description.
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 the verb and scope first and zero filler. Every word earns its place.
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 simple 2-parameter search with fully documented schema and no output schema, the description covers enough to invoke it. However, it omits what the search returns and how results should be used, which matters given no output schema to fall back on.
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 100%, so both the query and category parameters are already fully documented in the schema, including the category enum and defaults. The description only restates the searched item types and adds no syntax or matching-behavior detail beyond the schema.
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 (Searches) and resource (Ableton Live 12 Browser) and enumerates the item types it covers. It clearly conveys what it does, though it does not explicitly distinguish from close siblings like browser_load_item or browser_preview.
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?
Usage is only implied: an agent can infer this is the way to find browser items, but there is no explicit when-to-use guidance and no mention of pairing with browser_load_item to act on results. No exclusions or alternatives are stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.