VideoGenerationMCP

by AvivK5498

Overview Schema Source Related Servers Discussions Admin

Python

Local

generate_elevenlabs_voiceover

Synthesize speech with ElevenLabs for voiceover audio, saving to a temp file for video production.

Instructions

Synthesize speech with ElevenLabs and write the audio to a temp file.

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_id": "<voice_id>"
    },
    "name": "generate_elevenlabs_voiceover"
  }
}

Input Schema

Name	Required	Default
`seed`	No
`text`	Yes
`speed`	No
`style`	No
`language`	No
`model_id`	No	eleven_multilingual_v2
`voice_id`	Yes
`next_text`	No
`stability`	No
`output_path`	No
`output_format`	No	mp3_44100_128
`previous_text`	No
`with_timestamps`	No
`similarity_boost`	No
`use_speaker_boost`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 7, 2026

TDQS

B3.1/5.0

Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. It does mention the temp file side effect and the use of ElevenLabs, but it omits other important behaviors such as output format, return value, or whether the temp file is cleaned up. It provides some useful context but not comprehensive disclosure.

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?

The description is a single sentence, front-loaded with the core action, and contains no filler. It is appropriately concise for what it covers.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a complex tool with 15 parameters, no annotations, and no parameter descriptions. The one-sentence description covers only the basic action and side effect, leaving the agent without essential context like parameter roles, workflow placement, or prerequisites. It is minimally viable but insufficient for the tool's complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description contains no parameter information, and the input schema has no parameter descriptions (0% coverage). With 15 parameters, the agent receives zero guidance on what each parameter means, how they interact, or which are essential beyond the required text and voice_id.

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 tool's function: 'Synthesize speech with ElevenLabs and write the audio to a temp file.' It uses a specific verb ('synthesize') and resource ('ElevenLabs'), and the 'voiceover' in the tool name distinguishes it from siblings like generate_music or generate_sound_effect.

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?

No usage guidance is provided. The description only states what the tool does, with no mention of when to use it versus alternatives, prerequisites, or exclusions. The agent must infer from the tool name and siblings.

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