Skip to main content
Glama

get_browser_items_at_path

List the items inside an Ableton browser folder by path, returning each item's URI and whether it can be loaded, so you can choose the right instrument, effect, or sample to load next.

Instructions

What a browser folder contains, with each item's URI and whether it can be loaded (load it with load_instrument_or_effect).

Parameters:

  • path: "root/folder/subfolder", e.g. "drums/Drum Rack" or "plugins/Arturia". Roots: instruments, sounds, drums, audio_effects, midi_effects, plugins, user_library, packs, samples, max_for_live, current_project

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "path": "<path>"
    },
    "name": "get_browser_items_at_path"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden. It implicitly establishes a read-only lookup and enumerates the valid root names, which is real constraint information, but it says nothing about behavior on invalid or empty paths, recursion into subfolders, or listing size.

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 content is front-loaded and the parameter block is clearly separated, with nothing wasted. The opening is a sentence fragment rather than a clean statement of action, which slightly blunts the lead.

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?

With one parameter, an output schema already documenting the return shape, and no annotations, the description covers purpose, path construction, and the natural next step. The remaining gap is guidance on how this differs from the other browser-navigation tool.

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 coverage is 0% (path is a bare string), and the description fully compensates: it specifies the 'root/folder/subfolder' format, gives two concrete examples, and enumerates all nine valid roots. An agent can construct a correct path without any additional information.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The definition states a concrete resource (the contents of a browser folder at a given path) and what each result carries (URI plus a loadability flag), and it names the sibling that follows (load_instrument_or_effect). The phrasing is noun-first ('What a browser folder contains') rather than verb-first, so it is clear but slightly indirect.

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?

It gives an implied workflow: browse a folder here, then load an item with load_instrument_or_effect. It does not say when to use this instead of get_browser_tree, or whether the listing is recursive, so selection between the two browsing tools is left to inference.

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