Skip to main content
Glama
hermoso-ai

Hermoso

Official

Dub video

dub_video

Remake a video ad's voiceover into another language. Submit the source video URL and target language to receive a localized video with re-voiced and re-muxed audio.

Instructions

Remake a finished video ad's voiceover in another language (translated script, re-voiced, re-muxed). Paid; returns the served URL of the localized video.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
videoYesthe source video URL
scriptNothe original spoken script if known — improves translation fidelity
languageYestarget language, e.g. 'Spanish', 'de', 'French (Canada)'

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?

Annotations are all false, providing no behavioral info. The description adds value by disclosing it's paid and returns a served URL. It could mention non-destructive behavior, but overall adds useful context beyond annotations.

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?

One sentence with all key information: action, resource, payment, output format. No waste.

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 moderate complexity, the description covers purpose, output, and cost. Output schema exists, so return format is not needed. Complete for agent decision-making.

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

Parameters4/5

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

Schema coverage is 100% with parameter descriptions. The description adds meaning with terms like 'translated script, re-voiced, re-muxed' and improves interpretation of the 'script' parameter as improving fidelity.

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 action: 'Remake a finished video ad's voiceover in another language' with specific verb and resource. It distinguishes from sibling tools like change_voice and generate_voice.

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 provides clear context: it's for localizing finished video ads, it's paid, and returns a URL. It does not explicitly state when not to use it or list alternatives, but the context is sufficient.

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