Skip to main content
Glama

Outil.io

Generate video voiceover

generate_video_voiceover
Destructive

Générer une voix off naturelle (F1 Claire, F2 Élise, F3 Anne, F4 Léa, F5 Hélène, M1 Louis, M2 Victor, M3 Hugo, M4 Paul, M5 Marc) ; F = femme, M = homme. Crée un média audio et renvoie sa durée et des sous-titres avec temps des mots (relatifs au début de la voix : ajouter le at de la piste).

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": {
      "text": "<text>"
    },
    "name": "generate_video_voiceover"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
textYes
speedNo
voiceNoF2
languageNofr

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false / destructiveHint=true / openWorldHint=true; the description adds genuinely new behavior: it creates an audio media asset and returns a duration plus subtitles carrying per-word timings measured from the start of the voice. That output-shape disclosure is valuable given there is no output schema. It still omits rate limits, cost, and failure modes.

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

Conciseness3/5

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

Everything is packed into one long sentence with the ten-voice parenthetical dominating the middle, which pushes the important return-value detail to the end. Nothing is strictly wasted, but the structure is not front-loaded for the reader.

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 five-parameter, mutation-style generation tool with no output schema and no parameter descriptions, the definition covers the return values and voice codes but says nothing about text length limits, speed/language effects, or side effects. It is adequate to start a call but not complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across five parameters, so the description must compensate. It explains the voice enum meaningfully (F = femme, M = homme) but leaves 'text', 'name', 'speed' (0.7–1.4, default 1) and 'language' (six locales, default fr) entirely unexplained, and the trailing reference to 'le at de la piste' introduces a parameter that is not in the schema, adding confusion.

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 names a specific verb and resource ('Générer une voix off naturelle') and enumerates the exact voice identifiers the tool accepts, so an agent can tell it synthesizes speech. It does not differentiate itself from the sibling 'add_voiceover', so it stops 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance at all: nothing says whether to pick this versus add_voiceover, add_video_audio_track, or import_video_media_url. The only usable cue is implicit (it generates rather than attaches audio), which the agent must infer.

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.