Skip to main content
Glama

Outil.io

Add video caption

add_video_caption

Ajouter un texte ou sous-titre incrusté ; start/end sont des secondes 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>",
      "caption": "<caption>"
    },
    "name": "add_video_caption"
  }
}

Input Schema

NameRequiredDescriptionDefault
captionYes
versionYes
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / caption / properties / words
      Added value: +{
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "end": {
      +        "maximum": 3600,
      +        "minimum": 0,
      +        "type": "number"
      +      },
      +      "start": {
      +        "maximum": 3600,
      +        "minimum": 0,
      +        "type": "number"
      +      },
      +      "text": {
      +        "maxLength": 60,
      +        "minLength": 1,
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "text",
      +      "start",
      +      "end"
      +    ],
      +    "type": "object"
      +  },
      +  "maxItems": 80,
      +  "type": "array"
      +}
  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 readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is known. The description adds substantive context beyond that: it states the optimistic-concurrency contract (must supply the current montage version) and that the call returns a new version, plus that time values are on the montage timeline. It omits what happens on a stale version (conflict error vs. overwrite), which keeps it from a 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?

A single compact sentence-cluster with no filler; the unit clarification and the version requirement are both front-loaded. Its telegraphic style and switch between French prose and English tokens slightly reduce immediate parseability for an English-oriented model.

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 non-destructive mutation with annotations covering safety and no output schema, the description covers the key contract: units, preconditions, and that a new version comes back. It is not complete enough for a tool with a nested caption object containing an optional words array, since the agent gets no guidance on how caption-level times relate to word-level times or on failure modes.

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% with a nested caption object, so the description carries the full burden. It does add non-obvious meaning for 'start/end' (montage seconds, not source-frame timecode) and for 'version' (the current montage version, with a new one returned), which is genuinely beyond the schema. It leaves caption.id, text, and the nested words[] array entirely unexplained, and it is ambiguous whether the seconds note applies to words[].start/end as well.

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?

'Ajouter un texte ou sous-titre incrusté' names a specific verb and resource, and the 'incrusté' (burned-in) qualifier hints at a distinct artifact. It does not, however, distinguish itself from close siblings such as add_video_text or update_video_caption, so the agent must infer the boundary itself. The description is also written in French while the name/title are English, adding friction to matching.

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 prerequisite 'Exige la version actuelle du montage' tells the agent a read-then-write sequencing requirement, which is real usage guidance. But there is no explicit statement of when to choose this over add_video_text versus update_video_caption versus remove_video_caption, and no when-not guidance at all.

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.