Skip to main content
Glama

AIClipMaker.org

Re-cut a clip from an edited segment list

recut_clip
Destructive

Re-render one clip from a new list of source-video segments (the same engine behind the dashboard's clip editor). Times are seconds in the ORIGINAL source video: start from the clip's source_segments in list_clips (e.g. end 5 s earlier = lower the last end by 5). Segments are concatenated in the given order, so you can trim, extend, drop a dead moment in the middle, or reorder. Segments inside the clip's original range re-render in seconds; going outside needs the retained source video and re-runs the reframe engine.

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": {
      "job_id": "<job_id>",
      "clip_index": "<clip_index>",
      "segments": "<segments>"
    },
    "name": "recut_clip"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes
framingNoLayout override: 'full' shows the whole source frame (no side-cropping), 'track' forces the subject-tracking crop, 'auto' resets to the AI classifier. Omit to keep the clip's current framing. Non-auto values re-run the reframe engine and need the retained source video.
segmentsYesOrdered source segments the new clip is made of.
clip_indexYes0-based index from list_clips.
snap_to_wordsNoSnap each boundary onto transcript word boundaries (recommended).
reapply_captionsNoBurn default captions back on after the recut (default true).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With destructiveHint=true already declared, the description adds real operational cost signals: out-of-range segments 'need the retained source video' and 're-run the reframe engine'. It implies the existing clip is modified in place ('Omit to keep the clip's current framing') but never says plainly that the prior render is replaced — worth stating for a destructive tool.

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?

A single tight paragraph that front-loads the action, then the time-coordinate rule, then ordering semantics, then cost. No filler, though the sentence about trimming/extending/reordering is somewhat redundant with the concatenation rule just stated.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description should say what comes back — a new job id, an updated clip, whether it is synchronous — and it does not. Nor does it state that the original clip's render is overwritten. The segment and cost semantics are strong; the result contract is missing.

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 already 83%, so the bar is raised, yet the description still adds essential meaning: segment times are seconds in the ORIGINAL source video, order defines concatenation, and boundaries originate from list_clips. It complements the per-parameter descriptions rather than repeating them.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a concrete verb and resource ('Re-render one clip from a new list of source-video segments') and even identifies the underlying engine. It is clearly distinct from list_clips (which it cites as the source of segments) and from the other siblings, though it never explicitly contrasts itself with them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a concrete workflow anchor ('start from the clip's source_segments in list_clips') plus a worked example of a trim operation, and states the precondition for out-of-range edits (retained source video). It stops short of naming when to use a different tool or when a full re-process would be preferable.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources