Skip to main content
Glama
hermoso-ai

Hermoso

Official

Render ad video

render_ad

Turn a plan_ad's structured storyboard into a finished video ad with timed shots, clean voiceover, composited text, brand end card, and licensed music, rendered as one clip or stitched acts.

Instructions

RECOMMENDED for finished video ADS: render a plan_ad concept through the SAME quality pipeline as the Hermoso web Studio — timed shot list, exact/clean speech (no garbled words), text composited in post (never model-painted), brand end card, licensed music bed, real product references. Pass plan_ad’s full structured output as creative. Honors the plan’s render_plan structure/duration: a ≤15s storyboard renders as ONE single-pass clip; a longer plan automatically renders as STITCHED ACTS (fewest balanced ≤15s clips) — never time-compressed into one clip. Renders take 1–3 min; keep polling get_job if it returns still-rendering. Spends credits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelNovideo model id from hermoso_capabilities (default: the plan’s pick). Naming one is a DELIBERATE pick — the server asks before ever swapping it (no silent fallback)
musicNolicensed music bed on/off (default on)
dryRunNoreturn the routing decision (single pass vs stitched acts, resolved model + act lengths) WITHOUT submitting a render — free, nothing charged
lockupNopersistent brand-logo lockup overlay on/off
endCardNobranded end card on/off (default: on, except organic recipes)
captionsNocomposited caption pills on/off (default: the recipe decides)
creativeYesthe FULL structured output of plan_ad (must contain video_storyboard)
ttsVoiceNovoiceover voice name (e.g. Rachel / George) when the plan voices over
resolutionNo'720p' default; '480p' = cheap fast draft pass, '1080p'/'4k' = premium final delivery (more credits)
aspectRatioNooutput aspect ratio, e.g. 9:16 (default) / 1:1 / 16:9
durationSecondsNototal ad length in seconds — omit to honor the plan’s own duration

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)
inputNothe assembled render input (dry run only — resolved model, duration, scenes)
jobIdNothe render job id — poll get_job with this id to resume or inspect
modelNothe product-facing label of the model that rendered it
dryRunNotrue when this was a dry run (no job submitted, nothing charged)
jobTypeNothe routing decision — 'video' (single pass) or 'stitch' (acts)
stillRenderingNotrue when the render is still in progress — keep polling get_job with jobId
Behavior5/5

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

The description discloses rich behavioral traits beyond annotations: rendering pipeline quality, handling of short vs long plans (single pass vs stitched acts), compositing approach, and polling mechanic. No contradictions with annotations.

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 informative and front-loaded with the core purpose. While it is relatively long, every sentence adds value. Minor redundancy in listing defaults, but overall efficient.

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?

Given the tool's complexity (11 parameters, nested objects), the description covers rendering behavior, credit cost, polling, input requirements, and output expectations (implied by output schema). It provides sufficient context for an agent to use the tool correctly.

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

Parameters5/5

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

Although schema description coverage is 100%, the description adds critical meaning: e.g., 'creative' must be the full output of plan_ad, 'model' parameter warns against silent fallback, 'dryRun' explains cost-free routing decision. These enrich the schema significantly.

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 tool's purpose: 'render a plan_ad concept through the SAME quality pipeline as the Hermoso web Studio.' It specifies it is for finished video ads and distinguishes it from sibling tools by detailing the quality and behavior.

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?

The description gives explicit guidance on when to use the tool ('RECOMMENDED for finished video ADS') and provides context on rendering duration, polling requirements, and credit consumption. It lacks explicit exclusions or alternatives, but the context is clear enough.

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