Skip to main content
Glama

set_track_mute

Mute or unmute a specific track or return track in Ableton Live using its index and a boolean state. Use it to silence or restore audio during mixing or arrangement.

Instructions

Mute or unmute a track.

Parameters:

  • track_index: The track

  • mute: true mutes, false unmutes

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

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>",
      "mute": "<mute>"
    },
    "name": "set_track_mute"
  }
}

Input Schema

NameRequiredDescriptionDefault
muteYes
track_typeNotrack
track_indexYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden. It does add real context by revealing that track_type accepts 'return' as well as 'track', which tells the agent this tool reaches beyond regular tracks. However, it says nothing about whether the mute state persists, whether it interacts with solo, whether return-track indexing shares the same space as track indexing, or what errors occur on an invalid index.

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 single-sentence purpose is front-loaded and the parameter list is compact with no filler. The bullet for 'mute' largely restates the boolean name, which is minor waste but not harmful.

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?

An output schema exists, so return values need no explanation, and all three parameters are at least mentioned. For a mutation tool with zero annotation coverage, though, the description should clarify index semantics and the effect of muting on return tracks — the two things most likely to cause a mis-invocation.

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?

Schema description coverage is 0%, so the description must compensate, and it partially does: it enumerates all three parameters and supplies the 'track'/'return' enum values that the schema lacks entirely. But 'track_index: The track' is circular and omits the index base, valid range, and whether return tracks are indexed separately — a significant gap for the one required parameter.

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 states a specific verb and resource ('Mute or unmute a track'), which is unambiguous and immediately distinguishes it from siblings such as set_track_solo, set_track_volume, or set_track_arm. It does not explicitly name those siblings or explain the boundary, so it falls short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives or when not to use this tool. The intended use is only inferable from the tool name and the single sentence, which is the definition of implied usage at best.

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