Skip to main content
Glama
MCPGeneration-for-ElevenLabs

MCPGeneration-for-ElevenLabs

generate_music_from_video

Transforms one or more local videos into custom music tracks via ElevenLabs, requiring paid authorization and supporting cost controls.

Instructions

Generate music from one or more local videos using the documented video-to-music endpoint. Paid authorization is 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": {
      "video_paths": "<video_paths>",
      "filename": "<filename>"
    },
    "name": "generate_music_from_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNo
add_sfxNo
filenameYes
model_idNomusic_v1
allow_paidNo
descriptionNo
video_pathsYes
sign_with_c2paNo
separate_tracksNo
allow_unknown_costNo
use_audio_as_referenceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden and does disclose one useful behavioral fact: paid authorization is required. However, for a paid generation endpoint it omits whether output is an audio file or asset, whether the call is synchronous or asynchronous, cost implications, model behavior differences, and what side effects (e.g., C2PA signing, separate tracks) actually do.

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 sentences, front-loaded with the operation and followed by the authorization prerequisite. There is no filler or repetition, though the brevity is also the source of the documentation gaps rather than a model of efficient completeness.

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?

The tool is complex: 11 parameters, one enum, paid model selection, no output schema, and no annotations. The description addresses only the core action and one prerequisite, leaving the agent without enough information to choose models, understand cost controls, or correctly interpret most parameters.

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 coverage is 0% across 11 parameters, so the description must compensate. It adds meaning for video_paths ('one or more local videos') and hints at allow_paid via 'paid authorization,' but leaves filename, tags, model_id enum, add_sfx, description, sign_with_c2pa, separate_tracks, allow_unknown_cost, and use_audio_as_reference completely unexplained.

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: 'Generate music from one or more local videos,' which is clearly distinct from the audio-only siblings like generate_music. It also names the underlying 'video-to-music endpoint,' so an agent can tell what the tool does without opening the schema. It does not explicitly name an alternative sibling, but the video-input scope is distinctive.

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 only guidance is a prerequisite ('Paid authorization is required') and the implicit condition that you must have local video files. There is no explicit when-to-use vs when-not, and no routing advice relative to generate_music or generate_music_detailed. An agent must infer the selection criteria from the name alone.

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