Skip to main content
Glama

Outil.io

Add video layer

add_video_layer

Ajouter une piste vidéo superposée. at est le début dans le montage ; les dernières pistes sont au-dessus. Jusqu’à 6 superpositions. 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>",
      "layer": "<layer>"
    },
    "name": "add_video_layer"
  }
}

Input Schema

NameRequiredDescriptionDefault
layerYes
versionYes
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

B3.4/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description adds genuinely useful behavior: an optimistic-concurrency contract (current version required, new version returned) and a maximum of six overlays. It also explains stacking order ('les dernières pistes sont au-dessus'). It stops short of saying what happens on failure or whether the new version invalidates other callers.

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

Conciseness4/5

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

Four short sentences, front-loaded with the core action and constraints, with no filler. The only friction is that the definition is written in French while sibling tooling is presumably English, which slightly slows parsing rather than adding waste.

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?

Given a deeply nested schema, no output schema, and only hint-level annotations, the description covers the concurrency contract and overlay limit well. It leaves the rich nested parameter structure — the most error-prone part of the call — entirely unexplained, which is a meaningful gap for a mutation tool.

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 carries the full burden and only partly delivers: it clarifies 'at' as the timeline start and explains version semantics. projectId and the entire nested 'layer' object — mask, chroma, keyframes, transform, speed, volume, assetId — go undocumented in both schema and description.

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 opens with a specific verb and resource: 'Ajouter une piste vidéo superposée' (add an overlaid video layer), which is more precise than the bare title. It does not, however, contrast itself with closely named siblings such as add_video_clip or create_video_image_clip, so the agent must infer which layer-creation tool applies.

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 rather than stated: 'Jusqu'à 6 superpositions' tells the agent a hard limit exists, and 'Exige la version actuelle du montage' signals a precondition. But there is no explicit when-to-use versus alternative guidance, nor what to do when the version is stale (e.g. re-fetch via get_video_project).

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.