Skip to main content
Glama

generate_voiceover

Synthesize supplied text into narration audio with ElevenLabs; requires explicit upload permission and paid account credentials.

Instructions

Optionally synthesize supplied text with ElevenLabs. Explicit upload permission and paid account credentials required.

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>",
      "voiceId": "<voiceId>",
      "output": "<output>"
    },
    "name": "generate_voiceover"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
outputYes
voiceIdYes
authorizeUploadNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false. The description adds genuine context beyond them: this calls an external paid service and depends on an explicit upload authorization flag. It stops short of saying where the audio is written or what happens when authorization is absent, so it is additive but incomplete.

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?

Two tight sentences with the prerequisites front-and-center and no filler. It is efficient, though the 'Optionally' opening adds ambiguity rather than information.

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?

An output schema exists so return values need no explanation, but for a four-parameter external-service call with zero schema descriptions the definition is thin. The required 'output' destination, the voiceId source, and failure modes when credentials or permission are missing are all unaddressed.

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

Parameters2/5

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

Schema description coverage is 0% across four parameters, so the description carries the full burden. It loosely covers the input text, the upload authorization flag, and implies a voice selection via ElevenLabs, but never explains the required 'output' parameter, the voiceId format, or the 5000-character input limit.

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

Purpose3/5

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

The description names a specific action (synthesize text) and a specific external service (ElevenLabs), which is more concrete than the tool name alone. However, the word 'Optionally' hedges the core purpose and the definition never distinguishes this synthesis tool from the sibling generate_voiceover_script, so an agent must still guess at the boundary.

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?

There is no statement of when to use this tool versus alternatives such as generate_voiceover_script, and no exclusions. The only guidance is a prerequisite note about upload permission and paid credentials, which is useful but is not usage routing.

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