Skip to main content
Glama

video_inpaint

视频水印消除

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_inpaint"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

C2.5/5.0
Behavior2/5

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

Annotations declare readOnlyHint=false and openWorldHint=true, so the agent knows this invokes an external, mutating operation — the description adds nothing to that. It does not disclose the asynchronous task nature, that a job is queued and must be polled via the status endpoint (only hinted at in the callback_id schema field), nor anything about output location or processing time.

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?

It is as short as possible, but the brevity is under-specification rather than conciseness — there is no structure, no front-loaded scope, and not one sentence that helps the agent beyond the name.

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?

This is a multi-parameter video-processing mutation with no output schema and a third of parameters undocumented. For that complexity the description should explain that a job is created, how results are retrieved, and what the two unnamed parameters expect; it does none of this.

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 coverage is only 33%: callback_id is documented while video_url and workspace_id are not. The description is a single phrase and supplies no meaning for any parameter, so the two undocumented fields remain ambiguous (e.g., accepted URL forms, expected workspace scope).

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 concrete verb (消除/remove) and resource (视频水印/video watermark), so an agent can tell what the tool produces. It stops short of distinguishing itself from adjacent removal tools (video_magic_eraser, image_magic_eraser) or stating scope, so it is clear but not differentiated.

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?

The description contains no when-to-use guidance, no prerequisites, and no mention of alternative tools for related erasure tasks. The only signal is the topic itself, which the name already conveys.

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