Nativ

synthesize_audio_advanced

Synthesize multi-speaker audio/video with complete timing and review data.

    Billed operation. segments is a native array with text, start_ms,
    end_ms and optional original, speaker_id, voice_id, language_code and
    review fields returned by translation. speaker_voices maps each
    speaker_id to a preset or cloned voice_id. Pass stem_id to preserve
    background music and video_id to produce MP4. Outputs are local files
    (stdio) or expiring download URLs (hosted); no inline media blobs.

Input Schema

Name	Required	Default
`stem_id`	No
`language`	Yes
`segments`	Yes
`video_id`	No
`voice_id`	Yes
`output_path`	No	dubbed.wav
`language_code`	Yes
`speaker_voices`	No
`speech_islands`	No
`keep_same_length`	No
`source_transcript`	No
`video_output_path`	No
`source_duration_ms`	No
`document_translation`	No
`enterprise_long_form`	No
`keep_background_music`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.4/5.0

Behavior5/5

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

With no annotations provided, the description carries the full burden of transparency. It discloses vital behavioral traits including the output modalities (local files/expiring download URLs) and the crucial constraint that there are 'no inline media blobs.' This is highly effective behavioral context.

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 dense and technical, which is appropriate for an advanced API tool. While slightly run-on, every piece of information provided is highly specific and essential for tool understanding, preventing wasted words.

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?

Given the high complexity (16 parameters) and the lack of annotations, the description covers the most critical, high-level operational constraints (billing, output format, and segment structure). It provides enough context to handle the complexity without being exhaustive on every single parameter.

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?

With 0% schema description coverage, the description is highly valuable. It provides essential context for the complex `segments` array (explaining its internal fields) and `speaker_voices` mapping, which are not detailed in the raw schema structure.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly defines the tool's core function as multi-speaker audio/video synthesis. It differentiates itself by highlighting 'complete timing and review data,' suggesting a higher level of complexity compared to simpler synthesis tools like `synthesize_audio`.

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 provides important operational constraints, explicitly stating that it is a 'Billed operation.' This is a key piece of usage information that helps an agent determine when calling this tool is financially appropriate.

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

All Nativ tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.