Skip to main content
Glama

var2_motion_plan

Read-only

Free. Plan a motion-graphics piece WITH the user before building: send their request (+ references); you get 2–5 follow-up questions (tone, audience, voice-over and who speaks, music, background video, style, length) to ask them, then a proposal (concept, beats with exact on-screen words, voice, music, footage, price). Pass conversation back unchanged with answers or a note. Build the approved proposal with var2_motion_build.

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_motion_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNo
promptNoFirst call: the request, verbatim.
answersNo[{ questionId, optionIds?, text?, voice?, media?, skipped? }]
languageNoUser language (he / en …).
style_idNoThe chosen visual direction from catalog section=styles.
referencesNo[{ url (https), kind?: image|video|audio, role?: logo|photo|footage|music|voice, name? }]
aspect_ratioNo
brand_kit_idNo
conversationNoAs returned by the previous call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, and the description is consistent with a non-mutating planning call. It adds real behavioral context beyond that: the tool is free, returns 2–5 follow-up questions on a defined set of topics, then a proposal containing concept, beats, voice, music, footage and price. It does not cover latency or limits, so not a 5.

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 purpose and cost, then the call flow, then the handoff to the build tool. The parenthetical topic list and proposal field list are dense but each item is informative; slightly packed for a single paragraph.

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?

With no output schema, the description carries the burden of describing returns, and it does so for both phases (questions, then proposal contents including price). A 9-parameter tool with nested objects is mostly covered, though a few optional params remain unaddressed.

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

Parameters4/5

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

Schema coverage is 67%, and the description compensates by explaining the multi-call protocol: prompt is the verbatim first-call request, conversation must be passed back unchanged, and answers/note are the follow-up payloads. It leaves brand_kit_id and aspect_ratio unexplained, but the tricky stateful parameters are clarified.

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 ('Plan a motion-graphics piece') plus the scope qualifier 'WITH the user before building', which cleanly separates it from the sibling var2_motion_build that does the actual building.

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?

Explicitly says when to use it (before building, to gather requirements) and names the alternative for the next step ('Build the approved proposal with var2_motion_build'). It also gives the call sequence: first call with prompt, then pass conversation back with answers or a note.

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