Skip to main content
Glama

Outil.io

Set video caption style

set_video_caption_style
Destructive

Style de tous les sous-titres : karaoke (mot surligné, façon CapCut), bold, pop, boxed, clean ou none (masqués). maxWords = mots affichés à la fois. 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>",
      "style": "<style>"
    },
    "name": "set_video_caption_style"
  }
}

Input Schema

NameRequiredDescriptionDefault
styleYes
versionYes
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true, readOnlyHint=false and openWorldHint=false. The description adds genuinely useful behavior: the change affects every caption at once (explaining the destructiveness), the current version of the montage is required (optimistic concurrency), and a new version is returned. It still omits whether per-caption overrides are wiped or what happens on a version mismatch, so the addition is real but partial.

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?

Three dense sentences with the purpose front-loaded, then the style vocabulary, then the version contract. No filler, though the preset list plus parenthetical glosses makes the first sentence long and slightly harder to scan than a structured list would be.

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-parameter mutation with no output schema, the description covers the concurrency contract and the return value (new version) well. It leaves open whether existing custom caption styling is replaced, what the 'none' preset does to stored data, and which fields are mandatory inside the style object — meaningful gaps for a bulk edit tool.

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% across three top-level parameters and a nested style object with eight undocumented fields. The description compensates for the most important parts: the preset enum is enumerated with glosses, maxWords is defined, and 'version' is explained as the current montage version. projectId, font, size, color, position, highlight and uppercase remain undocumented anywhere, so compensation is incomplete.

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?

Specific verb+resource: it sets the style of ALL captions, which implicitly separates it from the per-caption siblings (add/update/remove_video_caption). The preset enumeration with a brief gloss for 'karaoke' and 'none' makes the operation concrete. No sibling is named explicitly, so it falls 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?

Usage is implied rather than stated: 'Style de tous les sous-titres' signals a project-wide bulk restyle, and the version requirement hints at an edit workflow. There is no explicit when-to-use vs. update_video_caption guidance, and no stated prerequisites such as ownership or lock state beyond the version.

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.