Skip to main content
Glama

update_track

Rename, enable/disable, lock/unlock video, audio, and subtitle tracks, and set Voice Isolation for audio tracks.

Instructions

Rename, enable/disable, lock/unlock a track; for audio tracks also set Voice Isolation.

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_type": "<track_type>",
      "index": "<index>"
    },
    "name": "update_track"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
indexYes
lockedNo
enabledNo
timelineNo
track_typeYes
voice_isolationNo
voice_isolation_amountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that this is a targeted field-level mutation and that Voice Isolation is audio-only, but it does not say what happens with an out-of-range index, whether renames must be unique, or whether changes are undoable.

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?

A single compact sentence that front-loads the core mutations and appends the conditional audio-only clause. No filler, no restatement of the tool name.

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?

For an 8-parameter mutation tool with no output schema and zero schema descriptions, the definition is only partially sufficient. The 'timeline' parameter and the semantics of 'index' are never addressed, and the relationship between voice_isolation and voice_isolation_amount is left to inference.

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 carry the burden. It maps meaning onto name, enabled, locked and voice_isolation, but leaves index, timeline, track_type and voice_isolation_amount completely unexplained, so roughly half the parameters remain opaque.

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 names a specific resource (track) and enumerates the concrete mutations: rename, enable/disable, lock/unlock, plus Voice Isolation for audio. That is far more informative than the bare name 'update_track' and implicitly separates it from add_track/delete_track, though it never explicitly contrasts with siblings like update_clip or update_item.

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 rather than stated: an agent learns that voice_isolation only applies to audio tracks, which is a genuine conditional rule. However, there is no guidance on when to prefer this over update_clip/update_item, no mention that track_type and index are required to target the track, and no prerequisites or failure conditions.

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