Skip to main content
Glama

track_add

Add video, audio, or subtitle tracks to the current timeline, letting you set count and audio format to build out the timeline structure before editing.

Instructions

Add tracks to the current timeline. type: video | audio | subtitle. audio_format: mono | stereo | 5.1 | 7.1 | adaptive1..36 …

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "track_add"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
typeNovideo
countNo
audio_formatNostereo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the behavioral burden. It communicates that tracks are added to the current timeline, but it does not explain permissions, reversibility, ordering, whether adding tracks modifies existing structure, or how count affects the operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loads the tool's purpose. However, the parameter details are written as terse fragments with a dangling ellipsis, which reduces clarity even though the overall length is appropriate.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a mutation tool with no annotations, no output schema, and four undocumented parameters. The description covers only a subset of the parameters and omits important behavioral context needed to invoke the tool confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description should compensate for all four parameters. It gives useful values for type and audio_format, but leaves name and count completely unexplained, and the audio_format enumeration is truncated with an ellipsis.

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 states a specific action and resource: adding tracks to the current timeline. It also names supported track types, making the tool distinguishable from unrelated add tools. However, it does not explicitly distinguish itself from the close sibling track_set.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies that this tool creates new tracks on the current timeline but gives no guidance on when to use it instead of track_set or other track-related tools. There are no stated prerequisites, exclusions, or alternative-routing instructions.

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