Skip to main content
Glama

Talking head: animate

talking_head_video

Animate a keyframe to a speech track (engine kling-ai-avatar-v2 or omnihuman-15; billed per second of speech, ≤ 60 s per segment).

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": {
      "keyframe_file": "<keyframe_file>",
      "speech_file": "<speech_file>"
    },
    "name": "talking_head_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
engineNokling-ai-avatar-v2
speech_fileYes
keyframe_fileYes
motion_promptNo
confirm_creditsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.6/5.0
Behavior4/5

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

Annotations only say this is a non-read-only, non-destructive, closed-world operation. The description adds genuinely new behavioral context: the available engines, that billing is metered per second of speech, and a hard 60 s per-segment limit — all material to an agent deciding whether to spend credits.

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?

A single sentence that front-loads the action and packs engines, billing model, and duration limit into a parenthetical without wasted words. Dense but readable; slightly compact for the amount of critical cost information it carries.

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?

An output schema exists, so return values need not be described, and the cost/duration constraints are covered. However, for a paid five-parameter mutation the description leaves confirm_credits and motion_prompt unexplained and gives no guidance on selecting between engines, which an agent cannot infer from structured fields alone.

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 five parameters, so the description has to compensate. It explains 'engine' by naming its two valid values and implicitly ties speech_file and keyframe_file to their roles, but 'motion_prompt' and especially 'confirm_credits' — the gate on a billed operation — get no explanation at all.

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 pair: animate a keyframe to a speech track. That is concrete enough to distinguish it from generic 'generate' or 'headshot', though it does not explicitly contrast with the close sibling 'lipsync', so sibling differentiation is only partial.

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 by the inputs (you need a keyframe and a speech file), and the 60 s segment cap hints at scope, but there is no explicit statement of when to choose this over lipsync or talking_head_keyframe, nor any stated prerequisites such as uploading files first.

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.

Resources