Skip to main content
Glama
Sign In

Instavar Video Templates and Studio

by com.instavar
OverviewDiscussionsAdmin

Scaffold carousel deck

scaffold_carousel_deck
Read-only

Build a deterministic editorial carousel deck from accepted copy. This does not render, save, or publish it.

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": {
      "templateId": "<templateId>",
      "hook": "<hook>",
      "points": "<points>",
      "payoff": "<payoff>"
    },
    "name": "scaffold_carousel_deck"
  }
}

Input Schema

NameRequiredDescriptionDefault
ctaNoOptional call to action on the final slide.
hookYesCover line on the first slide.
aspectNoSlide aspect ratio. Defaults to 4:5.4:5
handleNoOptional brand handle shown in the slide footer.
payoffYesClosing takeaway on the final slide.
pointsYesBody beats in order. listicle lists them on one slide, manifesto gives each its own slide, before-after uses the first as the problem and the last as the contrast, and value-first-reveal uses the first three.
subtitleNoOptional cover subtitle under the hook.
templateIdYesStory structure from list_carousel_templates.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • addedInput schema / properties / aspect / description
      Added value: +"Slide aspect ratio. Defaults to 4:5."
    • addedInput schema / properties / cta / description
      Added value: +"Optional call to action on the final slide."
    • addedInput schema / properties / handle / description
      Added value: +"Optional brand handle shown in the slide footer."
    • addedInput schema / properties / hook / description
      Added value: +"Cover line on the first slide."
    • addedInput schema / properties / payoff / description
      Added value: +"Closing takeaway on the final slide."
    • addedInput schema / properties / points / description
      Added value: +"Body beats in order. listicle lists them on one slide, manifesto gives each its own slide, before-after uses the first as the problem and the last as the contrast, and value-first-reveal uses the first three."
    • addedInput schema / properties / subtitle / description
      Added value: +"Optional cover subtitle under the hook."
    • addedInput schema / properties / templateId / description
      Added value: +"Story structure from list_carousel_templates."
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false; the description is consistent and reinforces this by explicitly saying it does not save or publish. It adds 'deterministic', which is useful behavioral context not conveyed by annotations. It stops short of describing the returned structure or how template/points influence slide count.

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?

Two sentences, front-loaded with the core action, and the second sentence non-redundantly rules out the most likely misconceptions (render/save/publish). No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 8 parameters, four of them required, and no output schema, the description doesn't explain what a 'deck' return value looks like (slide count, structure, determinism implications). It's adequate for triggering the tool but leaves the agent guessing about the response shape.

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 every parameter is already documented in the schema, including template-specific point semantics. The description adds only 'accepted copy' framing and no additional meaning to individual params, so the baseline 3 applies.

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+resource ('Build a deterministic editorial carousel deck') and the input it expects ('accepted copy'). The negation sentence clarifies boundaries relative to rendering/saving/publishing, though it doesn't name sibling tools like scaffold_video_spec or get_carousel_schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'From accepted copy' implies a precondition but never states when to choose this over scaffolding a video spec or fetching a template. The statement that it doesn't render/save/publish hints at follow-up steps without naming them, leaving routing to inference.

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