Skip to main content
Glama
Sign In

AskEditor

by com.askeditor
OverviewDiscussionsAdmin

Set clip keyframes

set_keyframes
Destructive

[write] Replace a clip's property keyframes. Values ease between keyframes and hold outside them. Keyframes animate position, scale, rotation, opacity, blur and colour at clip-local times; an empty list clears them. Use for push-ins, custom moves, blur-ins and fades to black and white. Not for adding one point to what is there (use add_keyframe) or preset motion (use set_clip_animation). Returns the changed clips' rows (with handles) and counts. Related: add_keyframe, set_clip_transform, set_clip_animation. Full docs: load_skill with tools: [name].

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

Input Schema

NameRequiredDescriptionDefault
idNoget_timeline handle.
itemsNoMany clips at once, max 60, each with this tool's fields.
keyframesNoKeyframes with add_keyframe's fields; [] clears them.
project_idYesThe AskEditor project this acts on (from list_projects).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already flag this as a destructive, non-read-only mutation, and the description reinforces that with a [write] marker and "Replace". Beyond that it discloses genuinely non-obvious behavior: interpolation semantics (values ease between keyframes, hold outside them), the empty-list clearing rule, and the return payload (changed clips' rows with handles, plus counts). It stops short of covering failure modes or how existing keyframes not in the list are discarded mid-range.

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?

Front-loaded with the verb and mutation flag, then usage, then exclusions, then return value, then related-tool pointers. Dense but every sentence carries distinct information; nothing restates the schema or annotations.

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?

For a destructive, 4-parameter write tool with no output schema, the description covers scope, clearing semantics, interpolation behavior, return shape, and the alternative routes. There is no output schema, so it correctly takes on the burden of describing what comes back.

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 the baseline is 3, but the description adds real meaning: "at clip-local times" clarifies atMs, and the enumerated animatable properties (position, scale, rotation, opacity, blur, colour) map to the nested keyframe fields. Minor imprecision: "colour" loosely stands in for brightness/contrast/saturation, and the ease enum values go uninterpreted beyond the general ease/hold statement.

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?

Opens with a specific verb+resource pair, "Replace a clip's property keyframes", and immediately scopes it as replacement rather than addition. The following sentences make it unmistakable versus add_keyframe (single point) and set_clip_animation (preset motion), so an agent can route correctly without opening a 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?

Explicitly states both when to use ("push-ins, custom moves, blur-ins and fades to black and white") and when not to, naming the two alternatives and the condition that selects each. It also names the prerequisite project/timeline handle source via the schema and the docs escape hatch (load_skill).

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

All AskEditor toolsInspect
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