Skip to main content
Glama
avotsai

avots-mcp

by avotsai
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

face_swap_video

Swap a face in a video with a face from a photo, preserving original motion and scene. Requires user confirmation before submission.

Instructions

Swap a face in a target VIDEO with a source face from a photo, keeping the original motion + scene (powered by fal-ai/pixverse). ASYNC — returns a job_id; the caller MUST poll check_job until status="completed". Cost is duration-based (per second of the target clip), roughly 500-2000 tokens. TWO-STEP FLOW (confirmation REQUIRED, like generate_video — this is an expensive job): STEP 1 (preview) call WITHOUT confirmed → returns the estimated cost, submits nothing, reserves nothing. STEP 2 (submit) call again with confirmed=true → submits the job and reserves tokens. IMPORTANT: the model has NO face-only mode and takes no text prompt — it transfers the whole person from the source photo, so for a clean result the FACE PHOTO must be a head-and-shoulders portrait. A full-body source photo will drag the clothing into the result. Tell the user this if their source looks full-body. Use for "put my face in this video", "face-swap this clip", "replace the actor's face", reaction/meme videos, etc.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmedNoSet to true ONLY after the user has approved the spend. Without it (or false), the tool returns a preview card with estimated cost and does NOT submit.
face_image_urlYesSource face. A URL (external https:// or an avots-hosted /v1/files/<uuid>) of a close-up head-and-shoulders portrait. OR reuse a SAVED avatar: pass "avatar:<id>" or "avatar:<name>" (see list_avatars) to use that stored face.
target_video_urlYesURL of the target video whose face will be replaced. Accepts an external https:// URL or an avots-hosted /v1/files/<uuid> URL.

Tool Definition Quality

A4.7/5.0
Behavior5/5

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

With no annotations, the description fully discloses async polling, two-step flow, cost range, and the critical limitation of transferring the whole person. Instructions like 'Tell the user this if their source looks full-body' show high transparency.

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?

Well-structured with clear sections (purpose, async, cost, two-step, important, use cases). Every sentence is informative; no fluff. Front-loads the core purpose.

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?

Covers all necessary aspects: async behavior, polling, cost estimation, confirmation flow, input requirements, and use cases. No output schema is compensated by detailed explanation of return behavior (job_id, preview card, cost).

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 coverage is 100%, but the description adds significant context: explains the confirmed parameter's role in the two-step flow, specifies 'head-and-shoulders portrait' for face_image_url, and mentions avatar reuse. Exceeds baseline of 3.

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 function: 'Swap a face in a target VIDEO with a source face from a photo, keeping the original motion + scene'. It distinguishes from siblings like generate_video and lipsync_video by specifying the face-swap operation.

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

Usage Guidelines4/5

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

Provides explicit use cases ('put my face in this video') and important prerequisites (head-and-shoulders portrait). Mentions the two-step confirmation flow, but lacks explicit 'when not to use' or alternative tools beyond referencing generate_video.

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