Skip to main content
Glama
romanstark

Ableton Maestro

load_device

Search Ableton Live's browser for devices and load a selected device onto the currently selected track. Returns search candidates first, then confirms the load with a chosen URI or path.

Instructions

Search Live's browser and load a device onto the currently selected track.

Two-step process: with confirm=False, searches browser and returns candidate items
along with currently selected track info. With confirm=True and a chosen uri or item_path,
loads the item.

Args:
    query: Search string for browser items.
    root: Optional browser root category to search within.
    uri: Browser item URI returned from search step.
    item_path: Direct filesystem or library item path.
    limit: Maximum number of search candidates to return (defaults to 12).
    confirm: Confirmation flag required to execute loading.

Returns:
    Dictionary containing search candidates or device load verification details.

Note:
    Browser.load_item targets the current selection rather than an explicit track argument.
    Target track is determined by song.view.selected_track.
    Inside racks or drum racks, target destination is determined by rack.view.selected_chain
    or rack.view.selected_drum_pad.
    Instruments replace the track instrument, whereas audio/MIDI effects are appended.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uriNo
rootNo
limitNo
queryNo
confirmNo
item_pathNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It clearly discloses that the tool targets the currently selected track rather than an explicit track argument, explains rack/drum rack destination behavior, and notes that instruments replace while effects append. This is valuable behavior not inferable from the schema.

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 organized with a clear summary, step breakdown, Args list, Returns, and Notes. It is slightly lengthy but every section adds needed behavioral context. The most critical usage information is front-loaded in the first two sentences.

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?

Given no annotations, 6 parameters at 0% schema coverage, and an output schema present, the description provides a complete picture: how to search, how to confirm, what the parameters mean, the target-selection side effects, and the return value. An agent has enough to invoke it 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?

Schema description coverage is 0%, so the description must compensate. It explains each parameter's role (query, root, uri, item_path, limit, confirm) in the context of the two-step workflow, giving semantics beyond the bare schema names and defaults. It also clarifies the relationship between uri, item_path, and confirm.

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 has a clear verb+resource: 'Search Live's browser and load a device onto the currently selected track.' It explains a two-step search-then-confirm process, which distinguishes it from generic device operations and sibling tools like get_devices or lom_call.

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 explains the two-step workflow: first call with confirm=False to search, then call with confirm=True and a uri/item_path to load. It does not explicitly name sibling tools as alternatives, but the workflow guidance is enough for an agent to understand when to use confirm and why.

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

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/romanstark/ableton-maestro'

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