AskEditor

Trim clip

trim_clip

[write] Trim a clip's source window. Clamped to the media and a 300ms minimum. It sets the source in-point and/or the length on the timeline, and optionally the start. Use to cut the head or tail off a take. Not for cutting a clip in two (use split_clip) or closing the gap a trim leaves (use close_gap or ripple_timeline). Returns the changed clips' rows (with handles) and counts. Related: get_timeline, split_clip, close_gap.

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": "trim_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.
`startMs`	No	Timeline start, ms.
`durationMs`	No	Timeline length, ms.
`project_id`	Yes	The AskEditor project this acts on (from list_projects).
`clipStartMs`	No	In-point into the source, ms.

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 it is a non-read-only, non-destructive, non-idempotent write. The description adds real context beyond that: clamping to media bounds, a 300ms minimum duration, exactly which fields get set (source in-point, timeline length, optionally start), and the return payload (changed clip rows with handles plus counts). It stops short of stating reversibility/undo or how batch failure is handled.

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 action and constraint, then usage, exclusions, and returns — every sentence carries information. Minor redundancy: the trailing "Related: get_timeline, split_clip, close_gap" repeats siblings already named earlier in the text.

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 clip rows with handles, plus counts). Combined with the clamping rules, field semantics, and explicit sibling routing, an agent has everything needed to invoke this 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, but the description maps the semantics of the mutation onto the parameters ("sets the source in-point and/or the length on the timeline, and optionally the start"), which clarifies the roles of clipStartMs, durationMs and startMs beyond their terse schema labels. It does not mention the `items` batch field (max 60) explicitly, so the multi-clip path stays schema-only.

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 description opens with a specific verb+resource ("Trim a clip's source window") and immediately constrains scope ("Clamped to the media and a 300ms minimum"). It explicitly names what it is not (split_clip, close_gap, ripple_timeline), so an agent can distinguish it from siblings 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 guidance ("Use to cut the head or tail off a take") and explicit exclusions with named alternatives for both edge cases: "Not for cutting a clip in two (use split_clip) or closing the gap a trim leaves (use close_gap or ripple_timeline)." This is textbook when/when-not/alternative routing.

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?