Skip to main content
Glama
Sign In
YoutuberBox

YoutuberBox

by saroby
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

generate_narration

Synthesize narration audio for video scenes using voicebox TTS and return per-scene durations.

Instructions

Synthesize narration audio for every scene (or the listed sceneIds) with voicebox TTS. Returns per-scene durations.

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": {
      "projectId": "<projectId>"
    },
    "name": "generate_narration"
  }
}

Input Schema

NameRequiredDescriptionDefault
voiceNoOverride the project voice
sceneIdsNoRegenerate only these scenes
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. Description does not disclose side effects (e.g., whether it modifies project state, overwrites existing narration), required permissions, or non-obvious behaviors like rate limits or cost implications.

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?

Two short sentences, no redundant information. Front-loaded with the core action and scope. Every phrase is informative.

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

Completeness3/5

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

Description covers the basic function and return value, but lacks prerequisites (e.g., project must exist, script required?), error cases, and details about output format beyond durations. Given 3 parameters and no output schema, it is adequate but not complete.

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% (voice and sceneIds documented). Description adds value by explaining that sceneIds are for regeneration and that the tool returns per-scene durations, which is not in the schema. However, the voice parameter is not elaborated beyond override.

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?

Description clearly states verb 'synthesize', resource 'narration audio', and scope 'for every scene (or the listed sceneIds)'. Distinguishes from sibling tools like generate_images and generate_captions which deal with other modalities.

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

Usage Guidelines3/5

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

Usage is implied by the tool purpose: use for generating narration audio. No explicit guidance on when to use or when not to use, nor alternatives. Sibling tools are not mentioned in the description.

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

Deploy Server

Other Tools