Skip to main content
Glama

add_track

Add a video, audio, or subtitle track at the top of a timeline, optionally naming it and selecting an audio channel format.

Instructions

Add a video, audio (with channel format) or subtitle track at the top, optionally naming it.

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

Input Schema

NameRequiredDescriptionDefault
nameNo
timelineNo
track_typeYes
audio_subtypeNo

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 establish that this is a non-read-only, non-destructive mutation, so the description does not need to repeat that. It adds useful context about placement at the top and audio channel formats, but omits whether insertion shifts existing tracks, required permissions, or what the operation returns.

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?

It is a single front-loaded sentence with no wasted wording. The action, resource, supported types, and placement are all stated efficiently.

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 four-parameter mutation tool with no output schema, the description covers the core action and most parameters but leaves timeline entirely unexplained. It is adequate for a simple insertion operation but not fully complete.

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 should compensate. It explains track_type variants, links audio_subtype to channel format, and explains the optional name, but completely omits the timeline parameter and does not clarify the audio_subtype enum values.

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 gives a specific verb and resource ("Add ... track") and enumerates the supported track types and placement ("at the top"). It is clear enough to distinguish from update_track and delete_track, though it does not name those siblings explicitly.

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?

It implies when to use the tool by describing the insertion position (top) and optional naming, but gives no explicit when-not guidance or prerequisites such as an open project or timeline. The alternative update_track is not mentioned.

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