Skip to main content
Glama
Sign In

Instavar Video Templates and Studio

by com.instavar
OverviewDiscussionsAdmin

Get a visual communication guide

get_creative_guide
Read-only

Read practical guidance before drafting concise plain or poetic copy, choosing carousel stories, designing visuals or recording human feedback. Returns guidance for the calling assistant to apply, not generated copy or saved feedback. Omit guideId to list guides.

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

Input Schema

NameRequiredDescriptionDefault
guideIdNoGuide to read. Omit to list the guides.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / guideId / description
      Added value: +"Guide to read. Omit to list the guides."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false. The description adds useful behavioral context by stating that it returns guidance for the assistant to apply rather than generated copy or saved feedback, and that omitting guideId lists available guides. It does not detail response formatting, but the added context is meaningful.

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 compact and front-loaded: the first sentence tells the agent when and what to read, the second clarifies return behavior, and the third explains listing behavior. Every sentence adds distinct information.

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

Completeness5/5

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

For a simple one-parameter read-only tool with no output schema, the description is complete enough. It covers when to use the tool, what is returned, what is not returned, and how to list guides, leaving no major ambiguity 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 description coverage is 100%, so the enum values and their meanings are already documented. The description adds semantic value by mapping the guide contexts to the user's workflow and explicitly stating that omitting guideId lists the guides.

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?

The description uses a specific verb and resource: 'Read practical guidance' and names the contexts it covers (copy, carousel stories, visuals, human feedback). It also clarifies what the tool does not return ('not generated copy or saved feedback'), making the purpose clear, though it does not explicitly distinguish itself from sibling tools by name.

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?

It states when to use the tool: 'before drafting concise plain or poetic copy, choosing carousel stories, designing visuals or recording human feedback.' It also explains the optional-parameter fallback ('Omit guideId to list guides'), but does not name alternative siblings or exclusions.

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