Skip to main content
Glama

Outil.io

Set video music

set_video_music
Destructive

Musique de fond en boucle sur tout le montage. duck=true baisse la musique quand une voix parle ; fade=true fondu d’entrée et de sortie. null retire la musique. Exige la version actuelle du montage ; renvoie la nouvelle version.

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>",
      "version": "<version>",
      "music": "<music>"
    },
    "name": "set_video_music"
  }
}

Input Schema

NameRequiredDescriptionDefault
musicYes
versionYes
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare it as a destructive, non-read-only mutation, so the baseline is lower, and the description still adds real behavior: the music loops across the entire edit, duck and fade change playback behavior, null removes music entirely, and the call requires the current version and returns a new one. This optimistic-concurrency requirement is exactly the kind of detail annotations cannot convey. It stops short of saying whether existing music is replaced or merged, or what happens on a stale version.

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?

Four short clauses, each earning its place: the core effect first, then the two flags, then the removal case, then the version/return contract. No filler, and the most important scoping fact (whole-edit loop) is front-loaded.

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

Completeness4/5

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

For a three-parameter destructive mutation with no output schema and no annotated field semantics, the description covers the essential contract: what it affects, flag behavior, removal via null, the version prerequisite, and that a new version is returned. What is missing — assetId/volume meaning and the replace-vs-merge outcome — is a real but bounded gap.

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

Parameters3/5

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

Schema description coverage is 0%, so the description carries compensation duty for three parameters. It explains duck, fade, null-removal for music and the meaning of version ("version actuelle du montage"), but says nothing about assetId (which asset source) or volume (range, units), so the top-level and nested numeric fields remain undocumented in both places.

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?

"Musique de fond en boucle sur tout le montage" names the resource (background music) and the scope (the whole edit, looped), which separates it from per-clip siblings like set_video_clip_volume. The verb itself is only implied ("set" from the name) rather than stated, so it is clear but not maximally sharp.

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?

The description gives concrete selection cues for its own parameter values — null removes the music, duck lowers it under speech, fade adds in/out ramps — so an agent knows how to configure it. It does not say when to prefer this tool over related ones (e.g. audio-track or clip-volume tools), leaving alternatives to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.