Simpler.Asia

studio.set_track_muted

Mute or unmute a whole track. A muted audio track plays nothing and a muted voice track stops ducking the music; a muted video-broll track keeps its pictures and drops its clips' own sound. The preview and the export both honor it, and each clip keeps its own muted and volume. Locked tracks may be muted. Refuses an unknown track_id or a text track, naming the fix.

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": {
      "project_id": "<project_id>",
      "track_id": "<track_id>",
      "muted": "<muted>"
    },
    "name": "studio.set_track_muted"
  }
}

Input Schema

Name	Required	Description
`muted`	Yes	true silences the track; false plays it again.
`track_id`	Yes	The track (vtr_) from get_composition's tracks.
`project_id`	Yes	The studio project (vp_…) this tool acts on.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations only declare readOnlyHint=false, so the description is carrying the burden and it does add real context: preview and export both honor the mute, per-clip mute/volume is preserved, locked tracks are allowed, and the tool refuses unknown track_ids and text tracks with a named fix. However, it does not state the return value or whether the operation is reversible beyond calling again, leaving some behavioral surface implicit.

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?

Four dense sentences, all front-loaded with the verb and scope before the per-track-type effects. Every sentence conveys a distinct behavioral fact with no padding.

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 three-parameter mutation with no output schema, the description covers effects, scope, persistence across preview/export, locked-track handling, and failure modes. Only the response shape and idempotency (calling twice with the same value) are unstated, which is a minor gap.

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 coverage is 100%, so baseline is 3, but the description adds genuine meaning: track_id must be a real non-text track or the call is refused, and muted is a whole-track toggle that overrides nothing at the clip level. That goes beyond the schema's one-line parameter blurbs.

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?

Specific verb+resource: mute/unmute a whole track, with the scope word 'whole' immediately distinguishing it from clip-level muting done by update_clip. It then explains what muting means per track kind (audio, voice, video-broll), so the agent knows exactly which object is affected.

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?

Provides concrete selection conditions: use this for the entire track rather than per-clip state ('each clip keeps its own muted and volume'), and clarifies that locked tracks are still mutable, which is a real decision point against lock_track semantics. It does not name the clip-level alternative explicitly, so it stops short of full sibling routing.

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

All Simpler.Asia tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?