Skip to main content
Glama

Generate Long-Form Narration

generate_long_form

Generate long-form narration (up to 500,000 characters ≈ 9 hours of audio) as an async job. Requires a Pro subscription key. Kokoro narration voices only — Arabic (ar_*) and cloned (voice_*) voices are rejected by the Long-Form engine. For Arabic or cloned voices, use text_to_speech: scripts over its per-call cap queue as single background jobs, up to 50,000 characters, without chapter export. Returns a job id — poll get_job_status; parts render progressively and audio_url appears when completed.

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": {
      "input": "<input>"
    },
    "name": "generate_long_form"
  }
}

Input Schema

NameRequiredDescriptionDefault
toneNoTone preset.neutral
inputYesThe full script, up to 500,000 characters.
pitchNoPitch shift in semitones (-4 to 4).
speedNo
voiceNoKokoro voice id — call list_voices for the catalog.af_aoede
formatNomp3

Output Schema

NameRequiredDescriptionDefault
job_idYes
statusYes
input_charsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Beyond the annotations (readOnly=false, destructive=false), the description discloses the async job model, progressive part rendering, when audio_url populates, and the required subscription tier — none of which the annotations convey. It stops short of describing failure modes (e.g. what happens on partial render or job expiry), which keeps it off a 5 given this is a long-running, costly operation.

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?

Front-loads capability and scale, then constraints, then the routing rule to the sibling, then the return/polling contract. No sentence is filler; the parenthetical and em-dash usage keeps it dense without ambiguity.

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?

For an async generation tool with an output schema present, the description covers everything an agent needs: prerequisites, valid voice domain, size limit, sibling routing, and the full job-id → get_job_status → audio_url lifecycle. Return-field detail is correctly deferred to the output schema.

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 67%, and the description adds real meaning beyond it: the voice parameter's accepted family and the rejection of ar_*/voice_* ids constrain valid inputs in a way the schema's 'Kokoro voice id' alone does not. The remaining parameters (tone, pitch, speed, format) are self-describing with defaults and bounds, so the gap is small.

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?

States a specific verb and resource ("Generate long-form narration") plus the scope (up to 500,000 characters ≈ 9 hours) and execution model (async job). It explicitly distinguishes itself from text_to_speech by voice family and character cap, so an agent can choose between them without opening either schema.

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?

Names preconditions (Pro subscription key), exclusions (Arabic ar_* and cloned voice_* are rejected), and the exact alternative to use for those cases (text_to_speech with its 50,000-character cap and no chapter export). This is explicit when/when-not guidance with a named fallback.

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