Skip to main content
Glama

Outil.io

Update video caption

update_video_caption
Destructive

Modifier exactement le sous-titre portant cet id, avec son texte et ses temps 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": "update_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 flag destructiveHint=true and readOnlyHint=false, so the mutation profile is known. The description adds genuinely new behavior: an optimistic-concurrency requirement on the montage version and the fact that the new version is returned, which an agent cannot infer from the annotations. It stops short of saying the prior caption content is replaced/lost.

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 sentences, no filler, with the identity constraint ('portant cet id') and the version precondition front-loaded before the return value. Dense and ordered well; nothing redundant.

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, nested-object, three-parameter mutation with no output schema, the description does supply the version contract and return value. It is still silent on what is overwritten, on the 'words' sub-structure, on timing units, and on the failure mode for a stale version, so an agent could still call it incorrectly.

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 load. It covers the caption id, its text and its start/end timings, and the version parameter's role, but leaves projectId unexplained, says nothing about the optional nested 'words' array, and gives no unit for the timing numbers (the schema only bounds them 0-3600). Partial compensation, not full.

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 (modify) applied to a specific resource (the caption bearing this id) plus the fields it rewrites (text and montage timings). This is clearly distinguishable from add_video_caption and remove_video_caption by the 'portant cet id' framing, though no sibling is named 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?

Adds one real precondition: the current montage version must be supplied, which implies an edit-existing rather than create-new flow. It never says when to prefer this over set_video_caption_style or add_video_caption, and never states what happens on a version mismatch.

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.