Skip to main content
Glama

Set Track States

set_track_states

Sets mute, solo, and lock states on multiple video or audio tracks in the active sequence, validating every target before applying changes and optionally returning pre-write state for restore.

Instructions

Set mute, solo and lock on several video or audio tracks of the active sequence in one host command, with per-track readback. Every requested track is read first; if any target is out of range, unreadable or asks for a state this host cannot read and write (solo has no public ExtendScript API and is probed on the QE track), nothing is changed. snapshot: true returns the pre-write state of the same tracks as a restore payload this tool accepts unchanged; with no state fields at all it is a read-only capture.

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": {
      "tracks": "<tracks>"
    },
    "name": "set_track_states"
  }
}

Input Schema

NameRequiredDescriptionDefault
tracksYesTracks to read or change. Omit a state field to leave it as it is.
snapshotNoTrue to return data.restore, the pre-write state of every requested track in the shape of the tracks argument (default: false).
idempotency_keyNoOptional client-chosen key (1-128 chars of A-Z a-z 0-9 . _ : -) for this intended edit. Pass a fresh key per edit and reuse it only when retrying that same edit, for example after a client-side timeout. A repeat with the same tool, key and arguments is not run again: while the first call is running it fails with IDEMPOTENCY_IN_PROGRESS (poll get_last_operations); after it finished it returns the original outcome marked replayed. A definite failure with nothing applied (receipt outcome not_applied) may be retried with the same key. Reusing a key with different arguments fails with IDEMPOTENCY_KEY_REUSED. Scoped to this MCP session (the stdio server process, or the HTTP server process when Streamable HTTP is stateless per request) and held in memory only (200 keys, 1 hour); it does not survive a restart or reconnect. Read-only invocations are never deduplicated.
expected_cep_targetNoOptional reviewed CEP sequence/clip identity and exact tick ranges. Checked before every generated command; UXP refuses this CEP-only guard.
expected_project_pathNoOptional absolute saved-project path. Every generated CEP command refuses before its body when the active project differs or is unsaved. UXP commands refuse this CEP-only guard; local-only tools do not inspect Premiere. Omit to keep existing behavior.

Output Schema

NameRequiredDescriptionDefault
okYesWhether the tool completed successfully.
dataNoTool-specific result data when ok is true; on failure, diagnostic detail when the tool provides it.
toolYesThe registered MCP tool name.
errorNoFailure detail when ok is false.
receiptNoVersioned common mutation receipt; success never implies rendered verification.
idempotencyNoPresent when idempotency_key deduplicated this call: replayed is true when the original outcome was returned instead of running again.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.30.0

TDQS

A4.1/5.0
Behavior5/5

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

Goes well past the annotations by disclosing atomicity ('nothing is changed' if any target is out of range or unreadable), the solo/QE probing limitation, and the restore-payload contract. These traits are consistent with readOnlyHint=false and destructiveHint=false — validation happens before any write, so the call is genuinely non-destructive.

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?

Three sentences, front-loaded with the action and followed by the failure rule and the snapshot option in a logical order. Some clauses are dense and parenthetical ('solo has no public ExtendScript API and is probed on the QE track'), but every sentence carries its weight.

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 five-parameter nested mutation with an output schema and partial annotations, this covers validation ordering, failure behavior, the snapshot contract, and a read-only mode. Marginal gaps remain around what the per-track readback contains and how partial-host-capability refusals are surfaced beyond the error name.

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 coverage is 100%, so the schema already carries parameter meaning; the description mostly restates it, notably the snapshot restore payload and the omit-a-field-to-leave-unchanged rule. The one idea that is easier to grasp from the description than the schema is the 'no state fields at all equals read-only capture' case, but that is also implied by the nested track item description.

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?

States a concrete verb and resource ('Set mute, solo and lock on several video or audio tracks of the active sequence') and pins down the batch scope ('in one host command, with per-track readback'). That batch framing implicitly separates it from per-track siblings like mute_track and lock_track, but it never names an alternative, so the differentiation is left to inference.

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 operational context: the all-or-nothing pre-read rule, the snapshot:true round-trip pattern, and the read-only capture mode when no state fields are supplied. It never says explicitly when to prefer a single-track sibling over this batch call, so exclusions are absent.

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