Skip to main content
Glama

Make voiceover

make_voiceover

Speak a script with an AI voice (3 credits per started 100 characters, 9 for gemini-kore), store it, and return word-timed caption segments. Pass voice to render_video and segments as captions.segments.

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": {
      "text": "<text>"
    },
    "name": "make_voiceover"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe script. For a 5s video, about 11 words.
startNoWhere the voice starts on the output timeline (s)
voiceNofable: Fable · British, warm; onyx: Onyx · deep, steady; nova: Nova · bright, friendly; shimmer: Shimmer · soft, clear; gemini-kore: Kore · follows the brand voicefable
brand_voiceNoDelivery notes, used by voices that take them (gemini-kore)
video_secondsNoThe clip's length: the result then says whether the timing works (pace, rushed last line, room for the end card)
end_card_secondsNoThe end card you'll render after the clip; 0 for none

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare that this is a non-destructive, open-world write; the description adds the material facts an agent needs: the operation is billable (3 credits per started 100 characters, 9 for gemini-kore) and it persists an asset ('store it'). It does not discuss regeneration/overwrite cost or whether re-running with the same script re-bills, which is the remaining gap.

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, zero filler, with the pricing parenthetical and the output description front-loaded before the hand-off instruction. Every clause carries information an agent would otherwise have to discover.

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?

With no output schema, the description correctly takes on describing returns (stored audio plus word-timed segments) and notes that video_seconds triggers a timing verdict. It leaves underspecified what identifier or handle the stored audio comes back under, which matters for a tool with six parameters and no output schema, but the overall picture is sufficient to call it correctly.

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 every parameter — including the voice enum, start offset, video_seconds pacing check, and end_card_seconds — is already documented, making 3 the baseline. The description adds one useful item beyond the schema, the cross-tool threading of the voice value into render_video, but explains none of the timing parameters itself.

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 uses a specific verb+resource ('Speak a script with an AI voice'), then names the two concrete outcomes: the stored audio and word-timed caption segments. An agent can tell exactly what this produces and how it differs from make_captions or make_music without opening the schema.

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?

It gives explicit downstream consumption guidance — 'Pass voice to render_video and segments as captions.segments' — which tells the agent what to do after calling. It stops short of stating when to prefer this over a sibling like make_captions, but the context for use is unambiguous.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources