Skip to main content
Glama

video_motion_control

视频动作控制

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

Input Schema

NameRequiredDescriptionDefault
modeNo
promptNo
image_urlNo
video_urlNo
callback_idNo自定义追踪 ID,会在 `/openapi/v1/work/status` 的结果里原样回传,用于对回你自己的业务单号(暂不支持 webhook 推送)
workspace_idNo
negative_promptNo
keep_original_soundNo
character_orientationNo角色朝向,默认与视频一致时可传 video

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.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false, so the safety profile is partly covered. The description adds nothing beyond that: it doesn't say this is an asynchronous task submission, whether mode selects different behaviors, what the required inputs are, or how long results take. For a 9-parameter generative video job, that is a substantial gap.

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?

At eight characters it is certainly short, but this is under-specification rather than conciseness. There is no structure, no front-loaded explanation of the operation, and nothing an agent can act on.

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?

A nine-parameter, non-idempotent, open-world video generation tool with no output schema and near-zero schema documentation needs a detailed description to be usable. This one provides none of that, leaving the agent unable to construct a valid call with confidence.

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

Parameters1/5

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

Schema description coverage is only 22%, and the description supplies no parameter meaning at all. Key parameters like mode, prompt, image_url, video_url, negative_prompt, keep_original_sound, and character_orientation are left undocumented in both the schema and the description, so an agent cannot tell which combination is required or how mode changes the call.

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 "视频动作控制" merely restates the tool name (video_motion_control) in Chinese and adds no verb-level detail about what the tool actually does to a video. It gives an agent no basis for distinguishing it from siblings such as video_character_swap, video_edit, or video_extend.

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, when not to, or which sibling to pick instead for closely related motion or character tasks. The agent must infer the tool's role entirely from its name.

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