Skip to main content
Glama

var2_save_motion_graphics

Free: save a COMPOSITION of catalog moments (+ brand_kit_id), a TEMPLATE (+ params), or a SPEC as an editable project; returns editor_url ("Refine in Motion Studio" opens it in the Studio). The user sees it play as a live draft in the chat. render:true also queues the MP4 (free; the chat shows the video when done) - after the user approved the draft. project_id updates / renders an existing piece in place. No compiler, no credits.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "var2_save_motion_graphics"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
specNoA Motion Spec (catalog language + recipes).
brandNoTemplates only: {name, colors, fonts, logo_url}.
paramsNoTemplate params (catalog template_id).
renderNoDefault false (save only; the user sees a live draft). true queues the MP4 - after the user approved the draft.
overlayNotrue = an OVERLAY for video: no background is painted, so on a var2_render_timeline "motion" track the video shows through. Alone it sits on black.
templateNoTemplate id (catalog section=templates).
project_idNoAn existing piece (from var2_motion_build / var2_read_motion_graphics / an earlier save): update and render it in place instead of creating a new project.
resolutionNo
compositionNo{styleId,seed,beats:[{componentId,params,durationFrames?,physics?,rotation?,scale?,join?}]}. Catalog components/styles/physics/joins define the valid values. One coherent story, varied moments.
aspect_ratioNo
brand_kit_idNoTemplates only.
duration_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations supply only a title, so the description carries the disclosure burden and does meaningful work: it names the returned editor_url, explains the 'Refine in Motion Studio' affordance, describes the live-draft-in-chat behavior, states that render queues an MP4 shown back in chat, and explicitly says there is no compiler and no credit cost. It still omits what project_id does to an existing project's prior content (overwrite vs version), any permission/auth requirement, and latency expectations for the queued render, which are the higher-risk unknowns for a mutation tool.

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?

Front-loaded with the core action and input modes, and nearly every clause carries information (cost, return value, render gating, in-place update). The parenthetical-heavy style and the 'No compiler, no credits' tail are slightly noisy, but no sentence is 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 13-parameter tool with nested objects and no output schema, the description still names the return value (editor_url) and the user-visible effects, which covers the most important unknowns. Gaps remain around how aspect_ratio/resolution/duration_seconds apply to each of the three input modes and what overlay does in combination with project_id, but the agent has enough to call it correctly in the common cases.

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 69%, so the schema already documents the key params, and the description's real contribution is grouping them into three mutually exclusive input modes (composition / template+params / spec) plus brand_kit_id, render, and project_id — a relationship the flat schema cannot express. It adds nothing for name, overlay, resolution, aspect_ratio, or duration_seconds, and does not say which combinations are valid despite zero required parameters.

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?

States a specific verb (save) and resource (an editable motion-graphics project) plus the three accepted input shapes (COMPOSITION, TEMPLATE, SPEC), which is far more than a restatement of the name. The one shortfall is that it never distinguishes itself from the closely named siblings var2_create_motion_graphics and var2_update_motion_graphics, so an agent must infer that 'save' is the persistence step rather than the creation step.

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?

Gives a real conditional: render:true should only be used 'after the user approved the draft', and project_id is the path for updating an existing piece instead of creating a new one. What it lacks is any routing to the obvious alternatives (var2_preview_motion_graphics for pre-approval drafts, var2_create_motion_graphics for initial generation), so the agent has to guess when this tool is the right entry point.

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