Skip to main content
Glama

var2_motion_build

Paid (per second of motion + voice-over). Build the proposal the user approved in var2_motion_plan: narration, then the motion spec, saved as an editable piece (studio_url). Music / background video must already be urls (library, uploads, or made first with var2_create_audio / var2_create_video — the tool says when). render:true also queues the 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": {
      "conversation": "<conversation>"
    },
    "name": "var2_motion_build"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
renderNoDefault false.
proposalNoThe approved proposal (default: the latest in the conversation).
resolutionNo
conversationYesFrom var2_motion_plan.
voice_asset_idNoOnly after state price_changed: the narration that build already paid for, reused instead of generated again.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only carry a title, so the description carries the burden and does well: it discloses the per-second billing model, that the output is a saved editable piece, that render:true additionally queues an MP4, and the voice_asset_id reuse rule tied to the price_changed state. It stops short of describing failure modes or what happens if the proposal is stale.

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?

Three sentences, front-loaded with the cost signal, then the core action, then prerequisites. The em-dash parenthetical about asset creation and 'the tool says when' is slightly fuzzy but overall the text is dense with useful information and free of filler.

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 6-parameter, nested-object, no-output-schema tool, the description covers cost, prerequisites, side effects, and the returned studio_url. Missing detail on resolution/name behavior and on how failures or stale proposals are surfaced, but nothing critical to invoking it correctly is absent.

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 67% and the description mostly restates schema hints (proposal default, voice_asset_id condition). The one genuine addition is that render:true queues the MP4 rather than just toggling a flag. The name and resolution parameters receive no explanation in either place, which is the main gap.

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?

States a specific verb and resource: builds the proposal approved in var2_motion_plan into an editable motion piece returned as studio_url, with narration then motion spec. This clearly distinguishes it from the planning sibling var2_motion_plan and the preview/save siblings.

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

Usage Guidelines5/5

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

Names prerequisites (proposal must already be approved in var2_motion_plan; music/background assets must already be URLs) and the exact alternatives for producing those assets (var2_create_audio / var2_create_video). It also flags the cost model up front so the agent knows the invocation is paid.

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.

Resources