Skip to main content
Glama

Outil.io

Set video mask

set_video_mask
Destructive

Appliquer ou retirer un masque : ellipse, ou rounded (coins arrondis, effet carte sur le fond 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>",
      "mask": "<mask>"
    },
    "name": "set_video_mask"
  }
}

Input Schema

NameRequiredDescriptionDefault
maskYes
clipIdYes
versionYes
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known; the description adds genuine context on top: an optimistic-concurrency requirement (must supply the current version) and the fact that it returns the new version. It stops short of saying that applying a mask replaces any existing one, which is the main destructive consequence.

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?

Two compact sentences, front-loaded with the action and options before the version/return contract. No filler, though the parenthetical gloss is the only mildly verbose element.

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 destructive mutation with no output schema, the description covers the version precondition and the return value ('renvoie la nouvelle version'), which is the most important missing piece. It still leaves the replacement semantics and error behavior on version conflict unstated, and the description is in French while the rest of the tool surface is English.

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% for four required parameters, so the description must compensate. It adds real meaning to 'mask' (explaining the rounded card effect) and to 'version' (must be the current one), but leaves 'projectId' and 'clipId' entirely unaddressed, including which clip in the project is targeted.

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?

States a specific verb pair (apply/remove) and resource (mask), and names the concrete options 'ellipse' and 'rounded' with a plain-language gloss ('coins arrondis, effet carte sur le fond du montage') that distinguishes it from sibling tools like set_video_background or set_video_transform. It does not explicitly contrast itself with a sibling, so it stops short of a 5.

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?

The apply/remove framing implies when to reach for it, and the 'Exige la version actuelle du montage' line gives a prerequisite. However, there is no explicit when-not guidance, no mention of which sibling to use for other visual effects, and no statement about what happens on a stale version beyond the implied requirement.

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.