AskEditor

Move clip

move_clip

[write] Move a clip to a new start time and/or lane. Dropped on an occupied lane it takes the lane and what it meets goes up a lane; a same-lane collision bumps to the next free lane. Use to reposition one clip freely. Not for swapping with a neighbour (use move_clip_to_neighbor), lining up with another clip's edge (use snap_clip) or shifting everything after a point (use ripple_timeline). Returns the changed clips' rows (with handles) and counts. Related: get_timeline, snap_clip, reorder_clip.

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

Input Schema

Name	Required	Description
`id`	No	get_timeline handle.
`items`	No	Many clips at once, max 60, each with this tool's fields.
`track`	No	New lane, 0 = bottom. Lanes then settle down: it stays over what it overlaps.
`startMs`	No	New start, 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.3/5.0

Behavior4/5

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

Annotations only declare the safety profile (readOnly=false, destructive=false, idempotent=false); the description adds genuinely non-obvious mutation semantics — displaced clips move up a lane, same-lane collisions bump to the next free lane — plus the return shape (changed rows with handles, and counts). It stops short of error/precondition behaviour (unknown handle, out-of-range startMs) and undoability, so it is strong but not complete.

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 the operation and its collision semantics, then the exclusions, then the return contract — a sensible ordering with no filler. The trailing "Related: get_timeline, snap_clip, reorder_clip" is mildly redundant since snap_clip was already invoked above, and reorder_clip is not differentiated anywhere.

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

Completeness4/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 correctly closes that gap by describing the return value, and it covers the collision behaviour an agent could not infer. The remaining hole is the batch capability (`items`, max 60) which the singular framing never addresses, and there is no note about required project_id scope.

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 baseline is 3; the description adds no parameter-level meaning beyond it. Notably it says nothing about the `items` array (up to 60 clips) or the relationship between the optional `id` and the batch path — only the plural "changed clips' rows" hints at batching.

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 verb and resource plus its two axes of change: "Move a clip to a new start time and/or lane." It then explicitly names the siblings it is not (move_clip_to_neighbor, snap_clip, ripple_timeline), so an agent can discriminate it from near-neighbours 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 an affirmative use case ("Use to reposition one clip freely") and three explicit when-not cases, each paired with the correct alternative tool. This is the strongest form of routing guidance in the sibling set.

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?