Instavar Video Templates and Studio

Propose a video storyboard

propose_video_storyboard

Read-only

Turn an ordinary video request into a three-beat visual proposal and recommended template. Pass templateId to preserve an accepted template when changing only the aspect; omit it for a new direction. This tool does not generate images, save a project, render, or publish.

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": {
      "brief": "<brief>"
    },
    "name": "propose_video_storyboard"
  }
}

Input Schema

Name	Required	Description	Default
`cta`	No	Accepted call to action, kept exactly as supplied.
`body`	No	Accepted body copy, kept exactly as supplied.
`brief`	Yes	The user's video request in their own words. It picks the recommended template and, without a title, the working title.
`title`	No	Accepted title, if the user supplied one. Omit to derive one from the brief.
`aspect`	No	Output aspect ratio. Defaults to 9:16.	9:16
`templateId`	No	Accepted template family to keep, for example when only the aspect changes. Omit for a new direction.
`acceptedDesign`	No	The design the user accepted: style, duration in seconds, audio, illustration and exclusions. Pass it on to scaffold_video_spec and later steps.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026

changedInput schema / properties / acceptedDesign / description

Previous value: -"The design the user accepted: style, duration in seconds, audio, illustration and exclusions. Pass it on to scaffold_video_spec and hosted tools."New value: +"The design the user accepted: style, duration in seconds, audio, illustration and exclusions. Pass it on to scaffold_video_spec and later steps."

Changed7 schema fields changedOct 29, 2026

addedInput schema / properties / acceptedDesign / description

Added value: +"The design the user accepted: style, duration in seconds, audio, illustration and exclusions. Pass it on to scaffold_video_spec and hosted tools."

addedInput schema / properties / aspect / description

Added value: +"Output aspect ratio. Defaults to 9:16."

addedInput schema / properties / body / description

Added value: +"Accepted body copy, kept exactly as supplied."

addedInput schema / properties / brief / description

Added value: +"The user's video request in their own words. It picks the recommended template and, without a title, the working title."

addedInput schema / properties / cta / description

Added value: +"Accepted call to action, kept exactly as supplied."

addedInput schema / properties / templateId / description

Added value: +"Accepted template family to keep, for example when only the aspect changes. Omit for a new direction."

addedInput schema / properties / title / description

Added value: +"Accepted title, if the user supplied one. Omit to derive one from the brief."

First observedOct 26, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false. The description adds useful behavioral context by stating that it does not generate images, save a project, render, or publish, and that the output is a proposal rather than an artifact. It stops short of describing return structure or limits, but the annotation coverage lowers that burden.

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?

The description is three sentences: purpose first, templateId decision rule second, exclusions third. It is front-loaded and contains no redundant exposition.

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 seven-parameter tool with a nested object and no output schema, the description gives enough context to understand purpose, boundaries, and the key templateId decision. Details of acceptedDesign and the handoff to scaffold_video_spec are left to the schema, which is acceptable given complete schema coverage.

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 100%, so all seven parameters, including the nested acceptedDesign object, are already documented in the schema. The description restates the templateId pass/omit rule but adds little beyond what the schema provides.

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?

It states a specific verb and resource: turn a video request into a three-beat visual proposal and recommended template. That is clear enough for an agent to understand the tool, but it does not explicitly distinguish it from siblings such as prepare_video_template or scaffold_video_spec.

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?

The description gives a concrete decision rule for templateId: pass it to preserve an accepted template when only the aspect changes, omit it for a new direction. It also clarifies actions the tool does not perform, though it does not name the sibling to use for those excluded actions.

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

All Instavar Video Templates and Studio tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.