Skip to main content
Glama
avotsai

avots-mcp

by avotsai
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

lipsync_video

Re-sync lips in an existing talking video to new spoken words. Dub a short clip by providing text for TTS or an audio track to match.

Instructions

Re-sync the lips in an existing talking VIDEO to NEW speech — video dubbing / re-voicing (powered by fal-ai/sync-lipsync). ASYNC — returns a job_id; the caller MUST poll check_job until status="completed" (usually 1-3 min). Returns a hosted MP4 URL on completion. TWO INPUT MODES: (A) provide text = the NEW words to say, and the server voices them with ElevenLabs TTS (auto-detects language incl. Russian; pick a voice preset) then lip-syncs; OR (B) provide audio_url = a ready voice/audio track to sync to (then text/voice are ignored). Exactly one of text or audio_url is required, plus video_url. The source clip must be a short talking-head video (front-facing face, max 20 seconds — longer clips are rejected; trim first). Use for "make this video say X", "dub this clip", "re-voice this video", "change what the person says". This is DIFFERENT from generate_talking_avatar (which makes a NEW talking face from a still portrait); lipsync_video edits an EXISTING video. TWO-STEP FLOW (confirmation REQUIRED — this reserves tokens): STEP 1 (preview) call WITHOUT confirmed → returns the estimated cost (TTS + lip-sync), submits nothing, reserves nothing. STEP 2 (submit) call again with confirmed=true → submits the job and reserves tokens. Cost typically 300-600 tokens.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textNoMode A: the NEW words the person should say (any language, read verbatim — no stage directions). Up to ~500 chars. Either this OR audio_url is required.
voiceNoMode A only: TTS voice preset — Aria, Sarah, Charlotte, Matilda (female) or Roger, George, Charlie, Brian (male). Default Aria. Ignored when audio_url is given.
audio_urlNoMode B: URL of a ready audio/voice track to lip-sync the video to (external https:// or avots /v1/files/<uuid>). When given, text/voice are ignored.
confirmedNoMust be true to actually submit + reserve tokens. Omit/false for a cost-only preview.
video_urlYesURL of the talking-head video to re-sync (max 20s, clear front-facing face). Accepts an external https:// URL or an avots-hosted /v1/files/<uuid> URL.

Tool Definition Quality

A4.8/5.0
Behavior5/5

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

No annotations provided, so description carries full burden. It explains async nature (job_id, polling check_job), hosted MP4 URL, two-step flow with confirmation and cost estimate, token reservation, and that longer clips are rejected. Also details Mode A: ElevenLabs TTS, auto-detect language, voice presets.

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?

Description is fairly long but well-structured: async note, input modes, two-step flow. Each sentence adds value; no fluff. Slightly dense but appropriate for the tool's complexity.

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

Completeness5/5

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

Given no output schema, the description covers all needed aspects: async behavior, polling, return format, two modes, constraints, costs, and two-step workflow. No gaps for correct usage.

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

Parameters4/5

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

Schema description coverage is 100% (all 5 parameters described), so baseline is 3. Description adds significant context: interaction between text and audio_url (exactly one required), voice only relevant in Mode A, confirmed for two-step flow, video_url constraints (max 20s, front-facing face).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Re-sync the lips in an existing talking VIDEO to NEW speech' and distinguishes it from sibling tool generate_talking_avatar (which creates a new talking face from a still portrait). The verb 'lipsync' and resource 'existing talking video' are specific.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly tells when to use this tool ('make this video say X', 'dub this clip', 're-voice this video'), contrasts with generate_talking_avatar, and details two input modes with conditions (exactly one of text or audio_url). Also provides constraints (max 20 seconds, front-facing face).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/avotsai/avots-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server