AskEditor

Set clip timing

set_clip_timing

[write] Set a clip's start and/or its timeline length directly. It keeps the source in-point (300 ms minimum, capped by the source unless it loops). Use to hold an image or a title longer, or to place a clip at an exact time. Not for changing where in the source it starts (use trim_clip). Returns the changed clips' rows (with handles) and counts. Related: trim_clip, set_clip_speed, ripple_timeline. 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_clip_timing"
  }
}

Input Schema

Name	Required	Description
`id`	No	get_timeline handle.
`items`	No	Many clips at once, max 60, each with this tool's fields.
`startMs`	No	Timeline start, ms.
`durationMs`	No	Timeline length (min 300), ms.
`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.8/5.0

Behavior5/5

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

Beyond the annotations (write, non-idempotent, non-destructive), it discloses key behavior: the source in-point is preserved, a 300 ms minimum applies, duration is capped by the source unless it loops, and the response contains the changed rows with handles plus counts. This is exactly the kind of context annotations cannot carry.

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?

Front-loaded with purpose, then constraints, then exclusions, then returns — a sensible order with no wasted sentences. The 'Full docs: load_skill' tail and Related list are slightly boilerplate but short.

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 compensates by describing the return value (changed clips' rows with handles and counts). Combined with the timing constraints and sibling routing, an agent has everything needed to call 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 baseline is 3; the description adds genuine meaning by explaining the interaction between start/duration and the source in-point, and the looping exception to the source-length cap. It doesn't explain the batch 'items' semantics in prose, but the schema already covers that.

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 opening sentence names a specific verb (set) and the exact fields affected (start and/or timeline length), with a [write] tag flagging mutation. It explicitly distinguishes itself from trim_clip, so an agent can route between the two without opening either 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 concrete positive use cases ('hold an image or a title longer', 'place a clip at an exact time') and an explicit exclusion with the alternative ('Not for changing where in the source it starts (use trim_clip)'). Related tools are listed as further routing context.

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?