Skip to main content
Glama
hermoso-ai

Hermoso

Official

Stitch multi-scene video

stitch_video

Combine multiple scenes into a single video for ads longer than 15 seconds. Specify scenes, voiceover, resolution, and aspect ratio to create a stitched ad.

Instructions

Render a multi-scene STITCHED video (≥2 scenes) — ONLY for spots LONGER than one model clip (>15s). A ≤15s multi-beat ad renders better and cheaper as ONE single-pass generate_video/render_ad on seedance-2 (it handles the full hook→demo→payoff arc in one take) — never stitch those. Blocks until done. Spends credits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelNovideo model id from hermoso_capabilities — omit to let the router pick
voiceNovoiceover voice name, e.g. Rachel / George
scenesYesarray of scene objects (visual + optional voiceover/seconds)
voiceoverNofull voiceover script spoken across the scenes
resolutionNo720p (default), 480p draft, or 1080p final
aspectRatioNooutput aspect ratio, e.g. 9:16 (default) / 1:1 / 16:9
durationSecondsNototal spot length in seconds (defaults to the sum of the scenes’ seconds)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
rawNothe raw job result payload (e.g. images[] for carousel template ads)
urlNothe served URL of the finished media (absent/null while still rendering)
jobIdNothe render job id — poll get_job with this id to resume or inspect
modelNothe product-facing label of the model that rendered it
stillRenderingNotrue when the render is still in progress — keep polling get_job with jobId
Behavior4/5

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

Adds context beyond annotations: 'Blocks until done' and 'Spends credits'. Annotations are all false (readOnlyHint, etc.), so no contradiction. Could mention side effects like job creation, but sufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four sentences, each providing critical information: purpose, usage guidance, blocking behavior, and cost implication. No fluff, front-loaded with key constraints.

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

Completeness4/5

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

Covers purpose, guidelines, blocking, and credits. Missing details about output format, but output schema exists. For a render tool with good annotations and schema, it is fairly complete.

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% (all 7 parameters documented in schema). Description does not add extra meaning about parameters beyond what schema provides. Baseline 3 is appropriate.

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 clearly states the verb 'Render a multi-scene STITCHED video' and specifies the resource (multi-scene stitched video) with a condition (≥2 scenes, >15s). It distinguishes from sibling tools like generate_video/render_ad for shorter spots.

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?

Explicitly states when to use (spots longer than 15s with ≥2 scenes) and when not to (≤15s multi-beat ad). Names the alternative tool (generate_video/render_ad on seedance-2).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/hermoso-ai/hermoso'

If you have feedback or need assistance with the MCP directory API, please join our Discord server