Skip to main content
Glama
Sign In

Instavar Video Templates and Studio

by com.instavar
OverviewDiscussionsAdmin

Prepare an announcement in Remotion or HyperFrames

prepare_announcement
Read-only

Prepare one paired announcement-card-v1 template, continue its caller-held project, edit copy or switch frameworks. Returns source files for local rendering. For the paired announcement-card-v1 or a HyperFrames announcement request, use prepare_announcement. Never infer a framework from creative wording. Omit framework unless the user explicitly chooses one or says no preference. If needs-selection, ask the user. Continue with the latest returned project and expectedRevision; apply edits through edits before switching. Keep the returned project document for later calls. Never describe this caller-held document as a saved hosted project. VideoSpec templates use prepare_video_template in either framework.

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

Input Schema

NameRequiredDescriptionDefault
copyNoAccepted copy for a new project only.
editsNoExplicit copy edits to apply before switching. Other source or timeline edits cannot be preserved.
projectNoThe latest project document returned by this tool. 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.
expectedRevisionNoRequired with project. Must match its revision. This checks the supplied document, not a server-side stored version.

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?

Beyond the readOnlyHint and destructiveHint annotations, the description discloses that the project is caller-held rather than a saved hosted project, that expectedRevision checks the supplied document rather than a server-side version, and that edits cannot preserve other source or timeline edits. These details materially affect how an agent should treat the returned document.

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 purpose is front-loaded and most sentences carry operational rules, but the description is dense and repeats the announcement-card-v1 routing instruction. It remains appropriately sized for a complex tool with nested parameters and caller-held state.

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 complex tool with five parameters, nested objects, and no output schema, the description covers the key behavioral context: source files are returned for local rendering, the project is caller-held, and revision handling is caller-side. It could say more about the returned source-file structure, but the essential invocation context is present.

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 baseline is 3, but the description adds useful semantics: framework should only be supplied for an explicit user choice, expectedRevision is required with project and must match its revision, and edits are applied before switching. It does not fully explain every nested field, but it meaningfully supplements the schema.

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: prepare one paired announcement-card-v1 template, continue its caller-held project, edit copy, or switch frameworks. It also distinguishes the tool from prepare_video_template, which handles VideoSpec templates in either framework.

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 routing rules: use prepare_announcement for paired announcement-card-v1 or HyperFrames announcement requests, use prepare_video_template for VideoSpec templates, omit framework unless the user explicitly chooses, and ask the user if needs-selection. It also explains how to continue with the latest returned project and expectedRevision.

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