Skip to main content
Glama

track_set

Modify a DaVinci Resolve track to rename, enable/disable, lock/unlock, delete, or adjust audio voice isolation settings for controlled timeline edits.

Instructions

Modify a track ('V2', 'A1', 'S1'): rename, enable/disable, lock/unlock, delete (irreversible), voice_isolation for audio tracks ({"isEnabled":true,"amount":70}).

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

Input Schema

NameRequiredDescriptionDefault
nameNo
trackYes
deleteNo
lockedNo
enabledNo
voice_isolationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations provided, the description carries the full behavioral burden. It does disclose the most important trait — that delete is irreversible — and notes voice_isolation applies only to audio tracks. But it says nothing about permissions/auth, whether operations are atomic, what happens to clips on a deleted track, or what the response contains for a mutation tool.

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 well-structured sentence front-loads the verb and resource, then lists operations parenthetically with the destructive one flagged inline. Every clause earns its place; nothing is redundant.

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 a six-parameter mutation tool with no annotations and no output schema, the description covers the operations and the key irreversible-risk fact. It is still incomplete on return behavior, error conditions for invalid track IDs, and whether parameters combine in a single call, which an agent would need before invoking confidently.

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 compensate for all six parameters. It does map nearly every parameter to an operation (name→rename, enabled→enable/disable, locked→lock/unlock, delete→delete, voice_isolation→the object example, track→ID format examples), which is solid value. It still leaves the exact voice_isolation object semantics (valid ranges, additional properties) and the nullable/default behavior unexplained.

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 specific verb and resource ('Modify a track') and enumerates the concrete operations it covers (rename, enable/disable, lock/unlock, delete, voice_isolation). It even gives valid track identifier examples ('V2', 'A1', 'S1'). It falls short of 5 only because it does not distinguish itself from related siblings such as voice_isolation, which it also touches as a parameter.

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 enumerated operations and the note that delete is irreversible, which cautions the agent. However, there is no explicit when-to-use vs. when-not guidance, no statement about whether multiple fields can be set in one call, and no pointer to alternative tools for adjacent tasks like adding a track (track_add).

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