AskEditor

Set transition

set_transition

Destructive

[write] Add, change or remove the transition where two clips meet on a lane. It belongs to the incoming clip. It can set every such seam at once. Use for fades, wipes, slides and zooms between shots; the clips must meet end to end first (use close_gap or move_clip). Not for audio or captions, or a clip's own entrance (use set_clip_animation). Returns the refreshed timeline table, transitions (into: the incoming clip's handle, type, durationMs), tracks and markers. Related: close_gap, get_timeline, set_clip_animation.

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

Input Schema

Name	Required	Description
`id`	No	The incoming clip's handle (after the cut).
`all`	No	Every seam instead of one clip.
`type`	No	Transition style; "none" removes it.
`items`	No	Many clips at once, max 60, each with this tool's fields.
`durationMs`	No	Length, ms, 100–2000. Default: kept, or the type's own (500; a whip its measured 333–533).
`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.4/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false; the description adds real context on top: the removal path is type='none', the operation can hit every seam at once, the clips must already be adjacent, and the response is a refreshed timeline/transitions table. It stops short of saying whether a removed transition can be restored, so not a 5.

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

Conciseness4/5

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

The [write] tag and the core action are front-loaded, and the safety-relevant exclusions come before the trailing 'Related:' line. A little is redundant with the schema's enum ('fades, wipes, slides and zooms') and the return-value sentence could be trimmed, but there is no filler.

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?

Six parameters, no output schema, yet the description still states what comes back (refreshed timeline table, transitions with into/type/durationMs, tracks, markers) and covers the batch cap and destructive path. Nothing critical for a correct call is missing.

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 coverage is 100%, so every parameter is already documented, including duration defaults and enum values. The description reinforces the meaning of `id` (the incoming clip's handle) and `all` (every seam at once) and adds the adjacency precondition, but that is mostly restatement of what the schema says. Baseline 3 is right when the schema carries the parameter load.

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?

States a specific mutation verb set (add/change/remove) on a precisely defined resource (the transition at a seam between two clips on a lane), plus the ownership rule ('belongs to the incoming clip'). An agent can distinguish it from set_clip_animation, close_gap, and move_clip without opening any 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?

Gives positive triggers (fades, wipes, slides, zooms between shots), a prerequisite with named remedies ('clips must meet end to end first (use close_gap or move_clip)'), and explicit exclusions with a routing alternative ('Not for audio or captions, or a clip's own entrance (use set_clip_animation)').

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?