Skip to main content
Glama
Hermoso

Hermoso

Official

Make an insert clip

make_insert

Generates a 1080x1920 reaction insert from an image or video and sound, timed to the sound's landing or a fixed 0.2–6 second length for post_edit joins.

Instructions

A reaction picture (image, or video from videoStart) with its sound, cut to when the sound lands (or seconds): a 1080x1920 clip for post_edit join.

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": {
      "sound": "<sound>"
    },
    "name": "make_insert"
  }
}

Input Schema

NameRequiredDescriptionDefault
imageNostill picture URL; use this or video
soundYessound URL (find_sound returns one), or a video whose own audio is used
videoNovideo URL to take the picture from, starting at videoStart
secondsNofixed insert length, 0.2 to 6 seconds, instead of when the sound lands
get_costNotrue: return the price only; nothing runs or bills
soundEndNoseconds into the sound where it ends
soundStartNoseconds into the sound where the insert's sound starts
videoStartNoseconds into the video where the insert starts
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. Changed3 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"
      +}
  2. Changed7 schema fields changedv0.1.465
    • addedInput schema / properties / image / description
      Added value: +"still picture URL; use this or video"
    • addedInput schema / properties / seconds / description
      Added value: +"fixed insert length, 0.2 to 6 seconds, instead of when the sound lands"
    • addedInput schema / properties / sound / description
      Added value: +"sound URL (find_sound returns one), or a video whose own audio is used"
    • addedInput schema / properties / soundEnd / description
      Added value: +"seconds into the sound where it ends"
    • addedInput schema / properties / soundStart / description
      Added value: +"seconds into the sound where the insert's sound starts"
    • addedInput schema / properties / video / description
      Added value: +"video URL to take the picture from, starting at videoStart"
    • addedInput schema / properties / videoStart / description
      Added value: +"seconds into the video where the insert starts"
  3. Addedv0.1.285

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already establish that this is a non-read-only, open-world, non-destructive operation, and the description adds useful behavioral detail about the 1080x1920 output and sound-synced timing. It does not explain billing behavior, failure modes, or what get_cost and expected_credits imply in practice, leaving meaningful gaps for a generation 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?

The description is a single dense sentence with no filler, and it front-loads the artifact being produced. Its parenthetical, noun-phrase structure is slightly fragmented and would be clearer with an explicit verb, but it remains compact and information-dense.

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?

For a 10-parameter generation tool with no output schema, the description covers the core artifact, output dimensions, source selection, and timing behavior. It is still thin on cost preview behavior, idempotency semantics, and what exactly is returned, relying heavily on the schema and annotations to fill those gaps.

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 the parameter meanings are already well documented in the schema. The description adds a little conceptual clarity about using image or video from videoStart and syncing sound to when it lands or to fixed seconds, but it does not add much beyond what the schema already states.

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 identifies a specific artifact: a 1080x1920 reaction clip made from an image or video plus sound, cut to when the sound lands or to fixed seconds. This is clear enough to distinguish it from generic video tools, but it never explicitly differentiates itself from nearby siblings such as insert_scene or clip_video.

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

Usage Guidelines2/5

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

The only usage hint is that the output is 'for post_edit join', which implies a downstream workflow but does not explain when to choose this tool over alternatives. There is no when-not-to-use guidance and no named alternative for similar insert or clip creation tasks.

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