Skip to main content
Glama

get_browser_tree

Returns Live's browser folders as an indented outline with each folder path, ready to use with get_browser_items_at_path. Filter by instruments, drums, effects, samples, packs, or user library.

Instructions

The folders of Live's browser, as an indented outline with the path of each folder (use the paths with get_browser_items_at_path).

Parameters:

  • category_type: "all", or one root: instruments, sounds, drums, audio_effects, midi_effects, plugins, user_library, packs, samples, max_for_live, current_project

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": "get_browser_tree"
  }
}

Input Schema

NameRequiredDescriptionDefault
category_typeNoall

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 full behavioral burden; the 'get' naming plus outline output make it clearly a non-mutating read, and it discloses the nesting/format of results. It says nothing about breadth (how deep the tree goes, size of the response, whether all categories are walked by default) or any performance implications of fetching everything.

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 purpose sentence is front-loaded and the enum list is compact bullet-style, both of which earn their space. The quoted parameter list is slightly verbose in formatting but adds no filler prose.

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?

Return values are covered by the output schema, and the one parameter's full value domain is enumerated in the description, so an agent has enough to call it correctly. The remaining gap is the absence of any size/scope expectation for the tree, which matters for a tool that can enumerate thousands of browser entries.

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

Parameters4/5

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

Schema coverage is 0% and the schema only declares category_type with a default of 'all', so the description is doing real work by enumerating every accepted value (instruments, sounds, drums, audio_effects, midi_effects, plugins, user_library, packs, samples, max_for_live, current_project) and clarifying that these are single root categories. It does not spell out whether the value is case-sensitive or what happens with an invalid value.

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 description names the exact resource ('the folders of Live's browser') and states the shape of the result (an indented outline with a path per folder). It implicitly distinguishes itself from get_browser_items_at_path by declaring this one yields paths for that tool, though no explicit verb ('list', 'get') frames the action.

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?

It gives explicit chaining guidance: 'use the paths with get_browser_items_at_path', telling the agent when this tool is a precursor and which sibling to call next. It does not state when-not-to-use or that only one category root can be fetched per call, so it stops short of a full routing rule.

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