mcp-face-transform

face_swap

Replace the face in the target image with the face from the source image. Provide both image URLs to perform the swap.

Instructions

Replace the face in target_image_url with the face from source_image_url.

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": {
      "source_image_url": "<source_image_url>",
      "target_image_url": "<target_image_url>"
    },
    "name": "face_swap"
  }
}

Input Schema

Name	Required	Description
`timeout`	No	Max upstream wait time in seconds (default 120).
`callback_url`	No	Optional webhook URL to receive the result asynchronously.
`source_image_url`	Yes	URL of the image whose face will be transplanted.
`target_image_url`	Yes	URL of the image that will receive the new face.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 18, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden. It only states the basic operation. It does not disclose whether multiple faces are handled, what happens if the source has no face, resolution limits, or whether the result is a new image or modification. The output schema exists but is not referenced.

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?

Single sentence, zero wasted words. The essential information is front-loaded. Perfectly concise for a straightforward operation.

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?

Given the tool's complexity (face swap with 4 parameters, output schema exists, multiple siblings), the description is too brief. It fails to explain failure modes, prerequisites, or output format. The agent is left with many unknowns.

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 coverage is 100% (all four parameters have descriptions). The description adds value by clarifying the relationship between the two required parameters (source face transplanted to target). However, it does not add extra syntax or format details beyond the schema. Baseline 3 is appropriate.

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 is a specific verb+resource: 'Replace the face in target_image_url with the face from source_image_url.' It clearly identifies the two images involved and the action, distinguishing it from siblings like face_cartoonize or face_beautify.

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

Usage Guidelines2/5

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

No guidance on when to use face_swap versus alternatives (e.g., face_change_age, face_detect_keypoints). No prerequisites, conditions, or exclusions are mentioned. The agent receives no context for choosing this tool over siblings.

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

Deploy Server