Skip to main content
Glama
Hermoso

Hermoso

Official

Clip a long video

clip_video

Cut one long video into several ranked, self-contained short clips with burned-in captions, ready to post to Reels, Shorts, or TikTok.

Instructions

Cut ONE long video into several RANKED, ready-to-post short clips (podcast, webinar, interview, talk, long ad cut -> Reels/Shorts/TikTok). Transcribes with timestamps, picks the strongest SELF-CONTAINED moments, then cuts + reframes each with ffmpeg — no video model renders anything, so it is fast and cheap. NOT supported: TikTok / Instagram / Facebook links, and anything age-restricted, private, members-only, geo-blocked or still LIVE — those fail fast with the real reason and are fully refunded, so ask for a direct file or an upload rather than retrying. SUBTITLES ARE BURNED IN BY DEFAULT (white sentence case timed by the spoken words, thin black outline, bottom safe band, no box) because short-form is watched on mute; captions:false for clean footage. TIMING IS APPROXIMATE (per-sentence, not word-level); never promise frame-accurate sync. Full rules: get_instructions({topic:'clip_video'}).

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>"
    },
    "name": "clip_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNohow many clips to cut, 1-8 (default 4)
videoYesthe long video to clip — a Vimeo/Loom/Dailymotion/Streamable/Rumble/Wistia/Twitch/TED watch URL, a direct https .mp4/.mov/.webm, or a Hermoso /generated/ URL; a URL, not a local file path; use upload_file for local files
captionsNoburn subtitles into every clip. DEFAULT TRUE — a clip cut from a podcast or a talk is watched on mute, and the words are the product. Set false for clean footage. A clip whose window carries no readable speech is delivered bare rather than captioned with a guess, and the result says which.
get_costNotrue: return the price only; nothing runs or bills
aspectRatioNoclip shape: '9:16' (default), '1:1', '16:9', any 'W:H', or 'keep' for the source framing
idempotency_keyNochosen once, resent unchanged on retries: the same key never buys twice
expected_creditsNothe get_cost price; refused unbilled if the live price differs

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.1.532
    • addedInput schema / properties / expected_credits
      Added value: +{
      +  "description": "the get_cost price; refused unbilled if the live price differs",
      +  "type": "number"
      +}
    • addedInput schema / properties / get_cost
      Added value: +{
      +  "description": "true: return the price only; nothing runs or bills",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / idempotency_key
      Added value: +{
      +  "description": "chosen once, resent unchanged on retries: the same key never buys twice",
      +  "type": "string"
      +}
    • changedInput schema / properties / video / description
      Previous value: -"the long video to clip — a YouTube/Vimeo/Loom/Dailymotion/Streamable/Rumble/Wistia/Twitch/TED watch URL, a direct https .mp4/.mov/.webm, or a Hermoso /generated/ URL; a URL, not a local file path; use upload_file for local files"New value: +"the long video to clip — a Vimeo/Loom/Dailymotion/Streamable/Rumble/Wistia/Twitch/TED watch URL, a direct https .mp4/.mov/.webm, or a Hermoso /generated/ URL; a URL, not a local file path; use upload_file for local files"
  2. Changed1 schema field changedv0.1.525
    • changedInput schema / properties / video / description
      Previous value: -"the long video to clip — a YouTube/Vimeo/Loom/Dailymotion/Streamable/Rumble/Wistia/Twitch/TED watch URL, a direct https .mp4/.mov/.webm, or a Hermoso /generated/ URL"New value: +"the long video to clip — a YouTube/Vimeo/Loom/Dailymotion/Streamable/Rumble/Wistia/Twitch/TED watch URL, a direct https .mp4/.mov/.webm, or a Hermoso /generated/ URL; a URL, not a local file path; use upload_file for local files"
  3. Changed2 schema fields changedv0.1.285
    • changedInput schema / properties / aspectRatio / description
      Previous value: -"clip shape — '9:16' (default) vertical for Reels/Shorts/TikTok; 'keep' leaves the source framing untouched"New value: +"clip shape: '9:16' (default), '1:1', '16:9', any 'W:H', or 'keep' for the source framing"
    • removedInput schema / properties / aspectRatio / enum
      Removed value: -[
      -  "9:16",
      -  "1:1",
      -  "16:9",
      -  "keep"
      -]
  4. Addedv0.1.161

TDQS

A4.4/5.0
Behavior5/5

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

Goes well past the annotations: discloses that failures 'fail fast with the real reason and are fully refunded', that subtitles are burned in by default with specific styling and a clean-footage opt-out, that a speechless window is delivered bare rather than mis-captioned, and that timing is per-sentence and never frame-accurate. That is exactly the operational context annotations cannot carry.

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-loads the core action and output before the caveats, and each sentence carries distinct information (unsupported sources, caption defaults, timing precision, pointer to get_instructions). The heavy capitalization and stacked parentheticals in the opening sentence add density without much cost in length.

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?

For a 7-parameter, open-world mutation tool with no output schema, the description covers source restrictions, billing/refund behavior on failure, caption output behavior, timing caveats, and where to find full rules. An agent can decide whether to call it and what to promise the user without opening anything else.

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 every parameter (count, video, captions, get_cost, aspectRatio, idempotency_key, expected_credits) is already documented in the schema. The description reinforces the captions default and its rationale but adds little new meaning about count, aspectRatio, or the cost/idempotency parameters beyond what the schema states.

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 ('Cut ONE long video into several RANKED, ready-to-post short clips') and enumerates the input genres (podcast, webinar, interview, talk, long ad cut) and the output formats (Reels/Shorts/TikTok). It also explains the mechanism ('cuts + reframes each with ffmpeg — no video model renders'), which separates it from generative siblings like generate_video or restyle_video without needing to name 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?

Gives an explicit exclusion list (TikTok/Instagram/Facebook links, age-restricted, private, members-only, geo-blocked, LIVE) and tells the agent what to do instead: 'ask for a direct file or an upload rather than retrying'. What is missing is routing to named sibling alternatives (e.g. reframe_video, add_subtitles, repurpose_video) when the task differs, but the when/when-not guidance is otherwise strong.

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

Deploy Server

Other Tools