Skip to main content
Glama

Lipsync

lipsync

Sync a video's mouth to an audio track (file ids from upload_file or previous outputs). Price depends on the rendered length; the result's credits_charged is the quote.

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_file": "<video_file>",
      "audio_file": "<audio_file>"
    },
    "name": "lipsync"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNo
audio_fileYes
video_fileYes
length_modeNo
confirm_creditsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.3/5.0
Behavior4/5

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

Beyond the annotations, which already declare this is a non-read-only but non-destructive closed-world operation, the description discloses the cost model (price scales with rendered length) and points at `credits_charged` as the quote. Remaining gaps are latency/processing behavior and whether repeated calls are safe.

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?

Two tight sentences, front-loaded with the core action and followed by cost context. Nothing is wasted, though the parenthetical about file ids could be folded more cleanly.

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?

An output schema exists, so return values need not be explained, but the description leaves a key workflow ambiguity: whether `confirm_credits` is required to accept the quote or whether a single call charges immediately. For a paid, 5-parameter generation tool this is a material omission.

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% and the description only illuminates `video_file`/`audio_file` by implying they are ids from `upload_file` or prior outputs. The three optional parameters (`model`, `length_mode`, `confirm_credits`) are given no meaning at all, and `confirm_credits` in particular appears to drive a spend-confirmation flow that the agent must understand to call this successfully.

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: 'Sync a video's mouth to an audio track'. This is distinctive, but the description offers no differentiation from nearby siblings such as talking_head_video or talking_head_keyframe, which also synthesize talking video content.

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?

It points to `upload_file` as the source of the two required file ids, which is useful prerequisite guidance. It never states when to choose this over the talking_head tools, nor any exclusions, so the choice between siblings stays implicit.

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