Skip to main content
Glama

Outil.io

Import video captions

import_video_captions
Destructive

Importer un SRT en remplaçant ou en complétant les textes. Les temps sont ceux du montage final. 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>",
      "srt": "<srt>",
      "mode": "<mode>"
    },
    "name": "import_video_captions"
  }
}

Input Schema

NameRequiredDescriptionDefault
srtYes
modeYes
versionYes
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the mutation risk is known. The description adds genuinely new behavior: timings are interpreted against the final edit's timeline, the current edit version is mandatory (optimistic concurrency), and the call returns a new version — all real operational facts not in the structured fields.

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

Conciseness5/5

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

Three short sentences, each carrying distinct information: the action and its two modes, the timeline semantics of the timings, and the version precondition plus return. Nothing is redundant and the action is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, four-required-parameter import with no output schema, the description covers the precondition, the mode semantics, and what comes back (the new version), which is the key return fact. Minor gaps remain on the expected SRT formatting and any size limits, but the agent has enough to call it correctly.

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 parameter meaning. It does explain mode semantically (replace vs append against existing texts) and clarifies version as the current edit version, but leaves srt (format, 200k max length) and projectId unexplained, so half the required parameters remain undocumented.

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 text names a specific verb (importer) and resource (un SRT de sous-titres) and states the two resulting behaviors (remplacer ou compléter les textes). It is distinguishable from siblings like add_video_caption (single caption) and get_video_captions_srt (read), though it never names an alternative 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?

Usage context is implied rather than spelled out: the replace/append choice maps to the mode parameter and the requirement of the current edit version tells the agent a precondition. There is no explicit statement of when to prefer this over add_video_caption or get_video_captions_srt, and no when-not guidance.

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.