Skip to main content
Glama

Outil.io

Add video text

add_video_text

Ajouter un texte animé (titre, sous-titre, bandeau, bulle, badge, appel à l’action) ; start/end en secondes MONTAGE. preset fixe le style, x/y le centre (0..1), animation pop/slideUp/slideLeft/typewriter/wordByWord/fade. 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>",
      "text": "<text>"
    },
    "name": "add_video_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
versionYes
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations only declare that this is a non-read-only, non-destructive, closed-world call; the description goes further by disclosing optimistic concurrency (the current montage version is required) and the mutation contract (the new version is returned). It also clarifies that start/end are in montage/timeline seconds rather than source seconds, which is non-obvious behavior. It does not say what happens on a version conflict, so it stops short of 5.

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?

The core action and the timing/version constraints are front-loaded, and the semicolon-separated clauses keep a dense payload readable. Some trailing enumerations of preset and animation values partly duplicate the schema enums, which is slightly redundant but still useful given 0% schema coverage.

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 with a nested 15-property text object and no output schema, the definition covers the essentials (action, timing units, coordinates, version contract, return value) but leaves most styling fields and the failure mode on a stale version unexplained. It is adequate to attempt a call, not complete enough to call it correctly on the first try without reading the schema.

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 prose carries the full burden, and it does add real meaning for several fields: start/end semantics and units, x/y as normalized center coordinates (0..1), preset as style selection, and the animation options. However, it leaves id, font, size, align, color, accent, uppercase and background entirely undocumented, and the preset prose (titre, sous-titre, bandeau, bulle, badge, appel à l'action) maps only loosely onto the enum (missing 'kinetic').

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 un texte animé') and enumerates the text kinds (titre, sous-titre, bandeau, bulle, badge, CTA), so an agent knows exactly what is being created. It never names the sibling tools (update_video_text / remove_video_text), so the add-vs-modify boundary is inferred from the verb rather than stated.

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 context is implied: use this to place new text on the montage timeline. The description adds one hard precondition ('Exige la version actuelle du montage') but gives no explicit when-not guidance, e.g. whether to use update_video_text for an element that already exists or what to do if the version is stale.

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.