Skip to main content
Glama
Sign In

Instavar Video Templates and Studio

by com.instavar
OverviewDiscussionsAdmin

Prepare a template video in Remotion or HyperFrames

prepare_video_template
Read-only

Validate one VideoSpec against the paired template contract and return local source for the chosen framework, or switch an existing project's framework. For a VideoSpec template in Remotion or HyperFrames, use prepare_video_template with the VideoSpec. Never infer a framework from creative wording; omit framework unless the user chose one or said no preference, and ask the user on needs-selection. Continue with the returned project: edit project.spec, then call again to regenerate or to switch frameworks. A rejected field is unsupported in both frameworks; fix it rather than dropping it. The tool returns local source and commands; it does not render, save or upload.

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": "prepare_video_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
specNoA VideoSpec 1.0 document for a new project.
projectNoThe latest project returned by this tool, with any edits made to project.spec. Caller-held, not a saved hosted project.
frameworkNoOnly supply an explicit user choice. Omit for an ambiguous request or to inherit the existing project framework.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, but the description adds important behavior: it returns local source and commands, does not render/save/upload, and rejected fields are unsupported in both frameworks. It also clarifies that the project is caller-held rather than a saved hosted project, which prevents misreading the framework-switch behavior as persistent mutation.

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 description is front-loaded and mostly efficient, with the core action and constraints stated early. A sentence such as 'For a VideoSpec template in Remotion or HyperFrames, use prepare_video_template with the VideoSpec' is slightly redundant with the opening, but the overall structure remains tight.

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 nested-object tool with no output schema, the description covers the essential contract: validation, local source and commands, no rendering/saving/uploading, and the caller-held project loop. It could say more about the returned source/commands shape, but it is sufficient for correct invocation.

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 100%, so the schema already documents the three parameters. The description still adds meaningful semantics for framework selection and project reuse, especially the rule to omit framework for ambiguous requests or to inherit the existing project framework.

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?

The description states a specific verb and resource: validate a VideoSpec against the paired template contract and return local source for Remotion or HyperFrames. It also distinguishes the framework-switching case and names the relevant input type, so an agent can identify the tool without opening the schema.

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?

It gives explicit usage rules: use it with a VideoSpec template, never infer a framework from creative wording, omit framework unless the user chose one, and ask the user on needs-selection. It also explains the follow-up loop: edit project.spec and call again to regenerate or switch frameworks.

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 toolsInspect
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.

Resources