Skip to main content
Glama

Outil.io

Add video clip

add_video_clip

Insérer un plan dans la piste vidéo principale. start/end sont en secondes dans le rush. Un id unique fourni par l’agent permet de retrouver le plan. 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>",
      "clip": "<clip>"
    },
    "name": "add_video_clip"
  }
}

Input Schema

NameRequiredDescriptionDefault
clipYes
indexNo
versionYes
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / clip / properties / mask / enum
      Previous value: -[
      -  "none",
      -  "ellipse"
      -]New value: +[
      +  "none",
      +  "ellipse",
      +  "rounded"
      +]
  2. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already mark this as a non-destructive write (readOnlyHint=false, destructiveHint=false), so the bar is lower. The description still adds meaningful behavior: it demands the current version of the edit (optimistic concurrency) and states that the new version is returned, which tells the agent the call is versioned and state-changing.

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?

Four short sentences, each purchasing distinct information: purpose, time unit semantics, id semantics, and versioning contract. Purpose is front-loaded and there is no filler.

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 mutation tool with no output schema and a deeply nested clip object at 0% schema coverage, the description covers the essential contract (versioning, time units, id) but leaves index and most nested clip fields undefined, so an agent still has to infer much of the payload.

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 clarifies start/end as seconds within the source footage, explains that the agent-supplied id is what lets the clip be retrieved later, and explains version as the current edit version. It says nothing about index (insert position) or the many nested clip fields (speed, volume, mask, keyframes, transform, transition, chroma), which remain undocumented.

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 opening sentence states a specific verb and resource: 'Insérer un plan dans la piste vidéo principale' (insert a clip into the main video track). The mention of the main track implicitly distinguishes it from sibling tools that add layers, text, or audio, though it never names one 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?

Usage is only implied: the tool targets the main video track, and the requirement for the current version suggests it belongs in a read-modify-write flow. There is no explicit when-to-use, when-not-to-use, or named alternative such as add_video_layer or move_video_clip.

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.