AskEditor

Animate clip

set_clip_animation

Destructive

[write] Animate a video, image, text or shape clip with entrance, exit and loop presets. Omitted sides are kept. "none" removes a side, and ids animates several. Use for quick motion on titles, stickers and stills. Not for custom moves (use set_keyframes) or cuts between clips (use set_transition). Returns the changed clips' rows (with handles) and counts. Related: set_keyframes, set_transition, add_text.

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": {
      "project_id": "<project_id>"
    },
    "name": "set_clip_animation"
  }
}

Input Schema

Name	Required	Description
`id`	No	get_timeline handle.
`in`	No	"none" removes it; typewriter is text only.
`ids`	No	More handles.
`out`	No	"none" removes it.
`inMs`	No	ms, 100–5000 (default 500).
`loop`	No	"none" removes it.
`items`	No	Many clips at once, max 60, each with this tool's fields.
`outMs`	No	ms, 100–5000 (default 500).
`loopSpeed`	No	0.25–4 (default 1).
`project_id`	Yes	The AskEditor project this acts on (from list_projects).

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the annotations, the description discloses important mutation behavior: omitted sides are kept, "none" removes a side, and ids can animate several clips at once. It also states that the tool returns changed clip rows with handles and counts, which is useful for a destructive write operation.

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?

The description is front-loaded with "[write]" and the core purpose, followed by behavior, usage boundaries, return behavior, and related tools. Every sentence carries useful information, and the structure is easy to scan.

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

Completeness5/5

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

With no output schema, the description supplies the return shape, and despite full schema coverage it still explains partial-update behavior and alternatives. For a 10-parameter mutation tool with annotations, it gives an agent everything needed to select and invoke it correctly.

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

Parameters4/5

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

Schema coverage is 100%, so parameter meaning is already well documented. The description still adds useful semantics about omitted sides being kept, "none" removing a side, and ids animating multiple clips, though it does not add much for timing or loopSpeed parameters beyond the schema.

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 states a specific verb and resource: animate a video, image, text, or shape clip using entrance, exit, and loop presets. It clearly distinguishes the tool from set_keyframes for custom moves and set_transition for cuts, so an agent can identify its role without opening the schema.

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

Usage Guidelines5/5

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

It explicitly says to use this for quick motion on titles, stickers, and stills, and explicitly says not to use it for custom moves or transitions, naming the correct alternatives. The when-to-use and when-not-to-use guidance is direct and actionable.

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

All AskEditor tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?