Montik

Add voiceover

add_voiceover

A voice reads a script (ElevenLabs) onto the Voiceover track from start. Write it the way it should be said: punctuation sets the pauses, and a short line per idea reads best in an ad. The file goes into the library like any upload. Counts against the workspace's monthly minutes of voice and music.

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>",
      "voice": "<voice>"
    },
    "name": "add_voiceover"
  }
}

Input Schema

Name	Required	Description
`text`	Yes	the script, up to 2500 characters
`start`	No	timeline seconds, default 0
`voice`	Yes	a name or id from list_voices
`volume`	No
`language`	No	ISO 639-1 code of the script, e.g. "de"; default: detected
`projectId`	No	Project to act on (default: the open one)
`approvalId`	No	Only after needs_approval: the id it gave, once the user said yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Beyond the annotations, the description discloses that the generated file is placed in the library like an upload and that it counts against the workspace's monthly voice and music minutes. Those are meaningful behavioral and billing details for an agent to know before invoking a non-read-only tool.

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 front-loaded with the core action and follows with practical guidance about pacing, file placement, and billing. The sentences are generally efficient, though the writing-style advice is somewhat indirect compared with the rest.

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?

For a seven-parameter mutation tool with no output schema and annotations covering safety, the description is largely complete: it explains the voiceover track, start position, library persistence, and quota impact. It leaves approval flow and the undocumented `volume` parameter to the schema.

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 high at 86%, so the schema already documents most parameters. The description adds useful meaning for `text` by advising punctuation and short lines per idea, and identifies ElevenLabs as the voice provider, but it does not clarify `volume` or add much beyond the schema for the other parameters.

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 states a specific verb and resource: a synthesized voice reads a script onto the Voiceover track. It distinguishes the tool from add_music and add_sfx by naming the Voiceover track, but it does not explicitly contrast itself with those siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives writing guidance for the script and mentions ad use, but it does not say when to choose add_voiceover over alternatives such as add_music, add_sfx, or add_text. Usage is only implied by the Voiceover track reference.

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

All Montik 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.

Resources

Need Help?