AskEditor

Split clip

split_clip

[write] Split a clip at absolute timeline time(s), N cuts in one call. Each cut sits at least 300ms from the clip's ends and its neighbours. For a compound's child, times are compound-local. Use before removing, moving or restyling part of a clip. Not for trimming an end (use trim_clip). Returns the changed clips' rows (with handles) and counts. Each new piece's handle is in changed. Related: get_timeline, ripple_delete_clip, delete_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": "split_clip"
  }
}

Input Schema

Name	Required	Description
`id`	No	get_timeline handle.
`atMs`	No	Cut time in timeline ms, or an array of them.
`items`	No	Many clips at once, max 60, each with this tool's fields.
`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.6/5.0

Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent write, so the safety profile is covered. The description adds genuinely extra behavior: a 300ms minimum separation from clip ends and neighbours, compound-local time semantics for child clips, and what the response contains (changed rows with handles, plus counts). It stops short of describing failure/error behavior when a cut violates the 300ms rule, which keeps it below 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.

Conciseness5/5

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

Front-loads the action and the batch capability, then constraints, then usage, then the trim_clip exclusion, then return shape. Every sentence carries non-redundant information, and the bracketed [write] prefix signals mutation immediately.

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?

For a mutation tool with no output schema, the description covers the constraints, the return shape, and the alternative tool, which is most of what an agent needs. It omits what happens on constraint violation (error vs. clamp) and any permission or state prerequisites, leaving a small gap.

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, but the description adds real meaning the schema lacks: times are absolute timeline positions (compound-local for a compound's child), a single call accepts N cuts (the atMs scalar-or-array union), and each cut must be ≥300ms from ends and neighbours — a constraint invisible in the schema. The items array's max of 60 is already in the schema, so no extra credit there.

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 ("Split a clip") plus the distinguishing capability "N cuts in one call" at absolute timeline times. It explicitly separates itself from trim_clip, so an agent can route between them 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 a positive trigger ("Use before removing, moving or restyling part of a clip") and an explicit exclusion with the named alternative ("Not for trimming an end (use trim_clip)"). The condition that selects the sibling tool is stated outright.

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?