Skip to main content
Glama

load_instrument_or_effect

Load an instrument, effect, preset, or plug-in by URI onto a regular, return, or master track. Use it to place browser items from Ableton Live at a specific track location.

Instructions

Load a browser item — instrument, effect, preset, plug-in, User Library file — onto a track, by its URI. Effects can also go on a return track (track_type="return", track_index 0 = A) or on the main track (track_type="master"). Find URIs with get_browser_items_at_path.

Parameters:

  • track_index: The track (return index for "return", ignored for "master")

  • uri: The item's URI, e.g. "query:Synths#Operator"

  • track_type: "track" (default), "return" or "master"

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": {
      "track_index": "<track_index>",
      "uri": "<uri>"
    },
    "name": "load_instrument_or_effect"
  }
}

Input Schema

NameRequiredDescriptionDefault
uriYes
track_typeNotrack
track_indexYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

A4.1/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. It usefully discloses that effects can target return and master tracks, that return index 0 means A, and that track_index is ignored for master. It does not say whether loading replaces an existing device on the track, what happens on URI mismatch, or what permissions/state are required — meaningful gaps for a mutation.

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?

Front-loaded with the core action in the first sentence, then a clean bulleted parameter block. Every sentence carries information, though the parameter bullets partially duplicate what could live in schema descriptions.

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?

An output schema exists, so return values need not be explained, and all three parameters are covered. For a three-parameter load operation with multiple destination modes, the description supplies the essential context; only side-effect behavior on the target track is left unaddressed.

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 description coverage is 0%, so the description must compensate, and it largely does: it documents all three parameters, including the non-obvious conditional semantics of track_index (return index for returns, ignored for master), the default value of track_type, and a concrete URI example. What is missing is any hint that track_index might be optional for master despite being listed as required.

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?

States a specific verb and resource ("Load a browser item ... onto a track, by its URI") and enumerates the item kinds covered: instrument, effect, preset, plug-in, User Library file. It also names the sibling that produces the input, so an agent can tell it apart from get_browser_items_at_path without opening either schema.

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?

Gives clear routing context: use get_browser_items_at_path to obtain URIs, and this tool to place them. It also spells out the three placement destinations and the default. There is no explicit when-not guidance (e.g., what to do if the target slot is already occupied), which keeps it off a 5.

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