Mute or unmute an audio or video track in a Premiere Pro timeline by specifying track type, zero-based index, and mute state. Toggling output on video tracks hides them from preview and export.
Mute/unmute a track (video tracks: toggle output)
| Name | Required | Description | Default |
|---|---|---|---|
| muted | Yes | ||
| trackType | Yes | Track type | |
| trackIndex | Yes | Track index, 0-based (V1 = 0, A1 = 0) |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It mentions mute/unmute and a video output toggle, but omits permissions, side effects, reversibility details beyond the implied toggle, and what happens for audio tracks.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single short sentence, front-loaded with the operation. The parenthetical is terse and somewhat ambiguous, but there is no filler or repetition.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a mutation tool with no annotations and no output schema, the definition is thin. It does not describe side effects, required context, or response behavior, leaving the agent to infer key operational details.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is moderate at 67%, with trackType and trackIndex documented in the schema. The description maps the muted boolean to mute/unmute behavior but adds no detail on track indexing or the trackType enum, so it does not meaningfully exceed the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource: mute/unmute a track, with a note that video tracks toggle output. It is distinguishable from clip-level mute by saying 'track,' but does not explicitly name or differentiate against sibling tools such as set_clip_mute.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No when-to-use conditions, prerequisites, or alternatives are stated. The parenthetical clarifies video-track behavior but not when to choose this over set_clip_mute, set_track_volume, or other track operations.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.