Skip to main content
Glama

add_music

Mix background music into a video by looping or trimming the track to match its length, with fades and optional ducking that lowers music during speech.

Instructions

Background music (a file path), looped or cut to the video's length, faded in and out. If the video has a voice, the music gets quieter while it speaks (duck).

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": "<video>",
      "music": "<music>"
    },
    "name": "add_music"
  }
}

Input Schema

NameRequiredDescriptionDefault
duckNo
musicYes
videoYes
volumeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations only declare this is a non-read-only, non-destructive, closed-world mutation. The description adds real behavioral detail beyond that: the track is looped or cut to video length, faded in/out, and automatically ducked under speech. It does not say whether the result overwrites the input video or produces a new asset, nor how failures are surfaced.

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 tight sentences, front-loaded with the core effect and then the conditional ducking rule. No filler or repetition.

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?

For a 4-parameter mutation with no output schema and zero schema coverage, the description conveys the audible outcome well but leaves the volume knob, defaults, and return/overwrite behavior undocumented.

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%, so the description must carry all parameter meaning. It explains 'music' as a file path and describes ducking behavior in prose, but never names the duck parameter or its default, and never mentions volume or its default of 0.25 at all.

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 names a concrete resource and effect: background music from a file path, looped or trimmed to the video's length and faded. It is clearly distinct from siblings like add_voice or add_captions, though the verb 'add' is only implied by the tool name rather than stated.

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 (use this when you want background music on a video), and it hints that ducking only applies when the video has a voice. There is no explicit when-not guidance and no named alternative among the many sibling video-editing tools.

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