Skip to main content
Glama

Render a video with a track

render_video

Put one of the user's tracks under a video, for example after adjust_track changed the scored track.

    duck lowers the music while people speak. music_volume and video_volume are gains from 0 to 2
    (1 leaves the level unchanged). Returns a link to the rendered MP4.
    

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_id": "<video_id>",
      "cue_id": "<cue_id>"
    },
    "name": "render_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
duckNo
cue_idYes
video_idYes
music_volumeNo
video_volumeNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare the write/idempotent/openWorld profile, and the description adds genuinely useful behavior: what duck does, the 0–2 gain range with 1 as neutral, and that the result is a link to an MP4. It does not address whether re-rendering creates a new artifact or overwrites one, nor whether rendering is long-running enough to require the wait_for_task/get_task siblings — meaningful gaps for a non-idempotent, open-world operation.

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?

The content is tight: an action sentence, an option gloss, and a return note, with nothing redundant. The ragged leading indentation and stray line breaks in the formatted text slightly hurt readability but cost no real estate.

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?

An output schema exists, so the return description is a bonus rather than a requirement, and the volume/duck semantics are well covered. What is missing for a five-parameter render tool is the meaning of cue_id and any hint about latency or task polling, which an agent needs in order to invoke it correctly.

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 coverage is 0%, so the description carries the parameter burden, and it does explain duck, music_volume, and video_volume including the neutral value of 1. However, the two required parameters video_id and cue_id are never explained, and cue_id is an opaque term an agent cannot resolve from the name alone.

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 opens with a concrete verb+resource pairing: putting a user's track under a video. That clearly separates it from siblings like get_track or analyze_video. It stops short of stating how it differs from the other video-side tools (score_video, import_video), so it falls just short of full sibling differentiation.

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

Usage Guidelines4/5

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

It supplies a real trigger context — use it after adjust_track has modified the scored track — which tells an agent where this fits in a workflow. It offers no exclusions or explicit alternatives, so there is no guidance on when a different video tool would be the better call.

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.