Skip to main content
Glama
hermoso-ai

Hermoso

Official

Change narrator voice

change_voice

Swap the narrator voice in a finished video while preserving performance, lip-sync, and background audio. Use when you like the video but want a different voice.

Instructions

Swap the narration of a finished video into a different voice — keeps the performance, lip-sync, and background sound. Use when the user likes the video but wants a different narrator voice; use dub_video only for language translation. Paid; returns the served URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
videoYesthe source video URL
voiceNotarget narrator voice preset name, e.g. 'Aria', 'George', 'Rachel', 'Sarah', 'Brian', 'Charlotte' (defaults to a warm female read)

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
Behavior5/5

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

Discloses key behaviors: preserves performance, lip-sync, background sound; returns served URL; paid. Annotations are minimal but description adds value without contradiction.

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?

Two sentences front-load action and preservation, then provide usage and cost. No unnecessary words.

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?

Comprehensive: covers purpose, usage alternatives, behavioral details, pricing. Output schema exists so return info not needed.

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 coverage is 100% with descriptions for both parameters. The description adds default voice note ('warm female read'), but doesn't significantly extend beyond schema.

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 'swap' and the resource 'narration of a finished video', specifying that performance, lip-sync, and background are preserved. It distinguishes from the sibling tool dub_video.

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?

Explicit guidance: use when user likes video but wants different narrator voice; use dub_video only for language translation. Also mentions paid status.

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