Skip to main content
Glama

extend_clip

Lengthens a video by starting a new clip from its last frame using your next-scene prompt, then joins both clips with the same model and settings.

Instructions

GPU. Makes a video longer without it falling apart: the last frame becomes the start of a new clip (same model and settings, your prompt for what happens next), then both are joined. Takes a render's time.

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": {
      "video": "<video>",
      "prompt": "<prompt>"
    },
    "name": "extend_clip"
  }
}

Input Schema

NameRequiredDescriptionDefault
videoYes
promptYes
secondsNo
transitionNocut

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations only declare non-read-only, non-destructive, non-open-world. The description adds genuinely useful behavior beyond that: the two-stage generation-plus-join pipeline, that model and settings are inherited from the source render, and a cost signal ('Takes a render's time'). It does not say whether the output is a new video asset or whether the original is preserved.

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?

Two front-loaded sentences with a useful 'GPU.' marker and no filler; the mechanism comes before the cost note. The phrase 'without it falling apart' is colorful but still carries the intent of seamless continuation.

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?

With no output schema and 0% parameter coverage, the description should close more gaps than it does. It explains the core operation well but leaves the two optional parameters, output shape, and whether the source clip is modified unspecified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% across four parameters. The description only clarifies 'prompt' (what happens next) and gestures at the join with 'both are joined', leaving 'seconds' and 'transition' (default 'cut') entirely undefined — no units, no valid values.

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?

States a concrete verb and resource ('Makes a video longer') and then explains the mechanism: the last frame seeds a new clip which is joined to the original. That mechanism implicitly separates it from loop_clip, reverse_clip, and trim_clip, though no sibling is named.

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

Usage Guidelines3/5

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

The description conveys the operational context ('your prompt for what happens next', 'Takes a render's time'), which implies you should reach for it when continuing action forward and warns about cost. It gives no explicit when-not guidance or named alternative such as loop_clip for repetition.

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