Skip to main content
Glama

add_voice

Place a voice line or any audio file onto a video clip at a set start time and volume, holding the last frame if the audio outlasts the clip.

Instructions

Puts a voice line (from make_voice, or any sound file) on a clip, starting at start seconds. If it is longer than the clip, the last frame is held until it ends.

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": {
      "video": "<video>",
      "audio": "<audio>"
    },
    "name": "add_voice"
  }
}

Input Schema

NameRequiredDescriptionDefault
audioYes
startNo
videoYes
volumeNo
keep_originalNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already disclose a non-destructive, non-open-world write, so the safety profile is covered. The description adds one genuinely useful behavioral fact not in structured data — audio longer than the clip holds the last frame — but says nothing about whether existing audio is replaced, how keep_original interacts with that, or what the call returns.

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?

Two short sentences, front-loaded with the core action and followed by the one edge case that matters. No padding, no restatement of the tool name.

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

Completeness2/5

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

For a 5-parameter mutation tool with zero schema coverage and no output schema, the description documents one parameter and one overflow rule, leaving volume scaling, keep_original semantics, and the video target unexplained. An agent could call it, but would be guessing on three inputs.

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 carries the full burden. It clarifies only `start` (units are seconds) and loosely identifies `audio` as a sound file; `video`, `volume`, and especially `keep_original` are left completely undefined, which is a real ambiguity for a write operation.

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 and resource ('puts a voice line ... on a clip') and identifies the typical producer of that audio ('from make_voice, or any sound file'), which lets an agent distinguish this from the caption/music/logo adders. It stops short of explicitly contrasting with add_music or add_text, so the sibling differentiation is implied rather than stated.

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 mention of 'from make_voice, or any sound file' hints at the intended workflow (generate with make_voice, then attach here) but never states when to use this instead of add_music, or what preconditions exist (e.g., clip must already exist). Usage is implied rather than prescribed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.