Skip to main content
Glama

video_character_swap

视频换脸

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "video_character_swap"
  }
}

Input Schema

NameRequiredDescriptionDefault
image_urlNo目标人脸参考图 URL
video_urlNo
callback_idNo自定义追踪 ID,会在 `/openapi/v1/work/status` 的结果里原样回传,用于对回你自己的业务单号(暂不支持 webhook 推送)
workspace_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / callback_id / description
      Previous value: -"自定义追踪 ID,webhook URL 后台配置"New value: +"自定义追踪 ID,会在 `/openapi/v1/work/status` 的结果里原样回传,用于对回你自己的业务单号(暂不支持 webhook 推送)"
  2. First observed

TDQS

D1.7/5.0
Behavior1/5

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

The annotations declare openWorldHint=true, readOnlyHint=false, idempotentHint=false, and destructiveHint=false, yet the description adds nothing about the asynchronous task model, processing time, or how results are retrieved. The presence of callback_id and a status endpoint in the schema strongly suggests a polling workflow, but the description never explains it.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The text is short only because it is under-specified, not because it is efficient. A four-character phrase that duplicates the tool name does not front-load useful information about inputs, behavior, or output.

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

Completeness1/5

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

This is a mutating, open-world async task with four parameters, no output schema, and no explanation of how to retrieve results. For that complexity, a bare label cannot be considered complete, leaving the agent unable to call the tool correctly without reading the schema in detail.

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?

With only 50% schema coverage, two of the four parameters (video_url and workspace_id) lack descriptions in both the schema and the tool description. The description references no parameters at all, so it does not compensate for the coverage gap or clarify how image_url relates to the source video.

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

Purpose2/5

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

The description "视频换脸" (video face swap) merely restates the tool name video_character_swap. It identifies the resource and operation only through tautology, but gives no scope, input/output framing, or differentiation from siblings such as video_inpaint or video_motion_control.

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?

There is no guidance on when to use this tool versus alternatives, and no prerequisites or exclusions. The name hints at face swapping, but an agent must infer entirely when this is preferable to other video-editing siblings.

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