Skip to main content
Glama

Outil.io

Move video track

move_video_track
Destructive

Placer une piste vidéo superposée ou audio à une seconde précise du montage. Exige la version actuelle du montage ; renvoie la nouvelle version.

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": {
      "projectId": "<projectId>",
      "version": "<version>",
      "clipId": "<clipId>",
      "at": "<at>"
    },
    "name": "move_video_track"
  }
}

Input Schema

NameRequiredDescriptionDefault
atYes
clipIdYes
versionYes
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already flag this as a destructive, non-read-only, closed-world mutation, so the bar is lower. The description usefully adds the version precondition and the fact that a new version is returned (valuable since there is no output schema), but it never explains what the destructive aspect actually threatens — e.g. whether a track occupying the target second is displaced, overwritten, or rejected.

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?

Two tight sentences with no padding, the primary action stated first and the version precondition second. Nothing is wasted, even if the choice of language differs from the English tool name and siblings.

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 four-required-parameter destructive mutation with no output schema and zero schema coverage, the description covers the critical operational facts: the anchoring unit, the version requirement, and the returned version. It stops short of describing collision/overwrite behavior on the destination second, which is the one thing an agent would most want before invoking a destructive move.

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, and it partially does: it clarifies that `at` is a second-position within the edit and that `version` is the current edit version whose successor is returned. It says nothing about `projectId` or how `clipId` identifies the track to move, leaving half the required parameters to be inferred.

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 concrete action and target: place an overlaid video or audio track at a precise second of the edit. That is far more specific than the bare name 'move_video_track', though the verb shifts from 'move' to 'place' and the resource wording mixes 'piste vidéo' with 'audio', leaving slight ambiguity about what exactly is being repositioned (the schema's `clipId` also sits oddly against the 'track' framing).

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?

One real usage constraint is given — it requires the current version of the edit — which tells the agent this is an optimistic-concurrency operation. But there is no guidance on when to choose this over siblings like move_video_clip, move_slide, or add_video_layer, and no stated exclusions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.