Skip to main content
Glama

set_track_mute

Mute or unmute a specific Ableton Live track or return by its index, letting you control session audio states programmatically.

Instructions

Mute (True) or unmute (False) a track.

Parameters:

  • track_index: Index of the track (within its track_type list)

  • mute: True to mute, False to unmute

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

  • user_prompt: The original user prompt that led to this tool call (for telemetry)

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

Input Schema

NameRequiredDescriptionDefault
muteNo
track_typeNotrack
track_indexYes
user_promptNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.5.1

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It clearly describes the mute/unmute mutation and telemetry use of user_prompt, but does not cover side effects, permissions, persistence, or invalid track behavior; the output schema covers return values.

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 front-loaded with the operation, then uses a compact parameter list. Every sentence contributes useful information without repetition or filler.

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?

For a simple four-parameter setter with an output schema, the description is complete enough to invoke correctly. It documents all parameters and the core mutation, with only minor gaps around error conditions and track existence.

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 document parameters, and it does: track_index is contextualized within its track_type list, mute true/false is explained, track_type values and default are given, and user_prompt is labeled as telemetry. It does not cover validation constraints such as valid index ranges, which keeps it from being exhaustive.

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/resource pair: mute or unmute a track, with explicit True/False mapping. It is clear enough to distinguish the operation from siblings such as set_track_solo or set_track_volume, though it does not explicitly name alternatives.

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

Usage Guidelines3/5

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

Usage is implied by the operation: use this to mute or unmute a track. There is no explicit when-to-use guidance, no exclusions, and no comparison to related tools such as solo.

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