Skip to main content
Glama

Preview a graphic

preview_graphic
Idempotent

Checks a template's data at once (its schema, and with source_text every figure against the script), then takes stills of the animated graphic in the brand's colours and fonts (brand_id's kit, or with project_id the project's). Returns a task_id; get_task gives the stills' image URLs in about 10 to 30 seconds. 1 credit a still.

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": {
      "template": "<template>",
      "data": "<data>"
    },
    "name": "preview_graphic"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYesThe template's data, matching its data_schema
brand_idNoA brand kit from list_brands (id or name). Brings the colours, fonts, logo, website and default copy (headline, call to action, small print); use instead of brand.
templateYesA template from list_graphics
placementNofull replaces the picture; right, left and band are overlays (each template lists the ones it takes)full
at_secondsNoWhen to take stills, in seconds into the graphic; default the middle and the last frame
project_idNoA long-form project: the stills use its brand kit, as its export will (brand_id, if also given, wins)
source_textNoThe script the figures come from; every figure in the data must appear in it

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the async contract (returns a task_id, polled via get_task), expected latency (about 10 to 30 seconds), and a per-unit cost (1 credit a still), plus the default still timing. These are exactly the traits annotations cannot express and that determine whether an agent should call it or warn the user about spend.

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 key information is front-loaded: what it checks, what it produces, then the task_id/latency/cost follow-up. It is dense with parenthetical asides, and the nesting of the brand/project rule inside parentheses is harder to parse than a separate sentence would be, but nothing is redundant.

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?

There is no output schema, and the description compensates fully by explaining the return value (a task_id), how to resolve it (get_task yields image URLs), how long that takes, and what it costs. For a mutation-flavoured async render tool with 7 parameters, nothing an agent needs in order to call it correctly is missing.

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 coverage is 100%, so the baseline is 3. The description does add genuine meaning on two parameters: source_text must contain every figure in the data, and brand_id wins over project_id's kit when both are supplied. Those are real precedence/validation rules beyond the schema, but the remaining parameters (placement, at_seconds, template) are left to the schema.

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 names a specific verb and resource: it validates a template's data against its schema and, optionally, every figure against source_text, then renders stills of the animated graphic. That is far more precise than the title's 'Preview a graphic'. It does not distinguish itself from likely sibling preview/export paths (e.g. preview_promo) or say when a still preview is preferred over a full render, which keeps it off a 5.

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?

Usage is implied rather than stated: 'Checks a template's data at once' conveys a validation-before-commit role, and the source_text clause implies a verification mode, but there is no explicit when-to-use, when-not-to-use, or named alternative. The only routing guidance is downstream (use get_task for the result).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources