Skip to main content
Glama

ad_clone_generate

视频复刻 — 生成

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": "ad_clone_generate"
  }
}

Input Schema

NameRequiredDescriptionDefault
ratioNo视频比例,空 = `9:16`
promptNoprompt(可在 Analyze 返回基础上修改)
durationNo生成时长(秒);不在可选值内(含不传)按 12
video_urlNo源视频片段 URL(Analyze 返回的 video_segment_url)
callback_idNo自定义追踪 ID,会在 `/openapi/v1/work/status` 的结果里原样回传,用于对回你自己的业务单号(暂不支持 webhook 推送)

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.8/5.0
Behavior3/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. The description contributes genuinely new behavioral context beyond them — that this is an asynchronous job submission whose response carries a task ID — but says nothing about polling (`get_work_status`), expected latency, cost, or what a failed submission looks like.

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

Conciseness3/5

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

There is no filler and the key fact (async submission) is front-loaded, but the brevity comes from under-specification rather than economy — two words of label plus one clause is not an appropriately sized description for a 5-parameter generation tool.

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

Completeness3/5

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

With 5 parameters, full schema coverage, and complete annotations, the definition is callable without guessing at argument syntax. What is missing is the workflow contract an agent actually needs for an async tool: that the returned `workspace_id` must be polled, and that the source video must first come from `ad_clone_analyze`.

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 description coverage is 100%, so every parameter (including the duration fallback to 12 and the empty-ratio default) is already documented in the schema. The description adds no syntax, format, or inter-parameter constraints beyond that baseline.

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

Purpose3/5

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

The label "视频复刻 — 生成" mostly restates the tool name, but the schema-level sentence adds a real fact: this submits an asynchronous generation task and returns a task ID (`workspace_id`). It still never says what 'video clone' produces or how it differs from siblings like `ad_clone_analyze` or `video_generate`.

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, when-not-to-use, or prerequisite guidance. The only hints that this follows `ad_clone_analyze` appear incidentally inside parameter descriptions ("可在 Analyze 返回基础上修改", "Analyze 返回的 video_segment_url"), not as stated workflow guidance.

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