Skip to main content
Glama

load_instrument_or_effect

Load instruments and effects onto any Ableton track via browser URI, with support for master and return tracks. Combine with device parameters to fine-tune the loaded device.

Instructions

Load an instrument or effect device onto a track by its browser URI.

Discover URIs with get_browser_tree / get_browser_items_at_path. After
loading, use get_device_parameters + set_device_parameter to dial it in.
Pass track='master' or track='return:0' to load onto the master bus or a
return track (e.g. a Reverb on a return, or the master-bus chain).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uriYes
trackNo
track_indexYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations are provided, so the description must disclose behavior. It adds context about loading onto master/return tracks and the follow-up workflow, but fails to mention side effects like whether an existing device is replaced, error handling for invalid URIs, or any prerequisites. This is partial disclosure for a write operation.

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 three sentences with no fluff: purpose, discovery workflow, and special track targeting. It is front-loaded and each sentence contributes distinct information.

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

Completeness3/5

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

The tool is moderately complex with multiple track addressing modes and a discovery dependency. The description covers URI discovery and master/return targeting, but omits track_index semantics and failure/error behavior. Since an output schema exists, return values don't need explanation, but the missing parameter nuance and side effects leave the description incomplete.

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

Parameters3/5

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

The schema has 3 parameters with zero description coverage. The description compensates for 'uri' by pointing to browser-tree discovery, and for 'track' by showing specific string values like 'master' and 'return:0'. However, 'track_index' (a required parameter) is not explained at all, leaving a key part of the input semantics vague.

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 'Load an instrument or effect device onto a track by its browser URI' with a specific verb and resource. It differentiates from siblings like get_browser_tree (discovery) and load_drum_kit (specific device type) by focusing on generic device loading.

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 explicitly instructs to discover URIs with get_browser_tree / get_browser_items_at_path, and to follow up with get_device_parameters and set_device_parameter. It also explains how to target master and return tracks via the 'track' parameter, but does not explicitly state when not to use this tool or name alternatives.

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

Install Server

Other Tools

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/verove-jordan/ableton12-mcp'

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