Skip to main content
Glama

Preview a promo's scenes

preview_promo

Stills of every scene of the planned promo at its settled frame, in one size, before rendering any clip. 1 credit a still, nothing for scenes already rendered.

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": {
      "promo_id": "<promo_id>"
    },
    "name": "preview_promo"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeNoThe size to see (9:16 by default)
promo_idYesThe promo's id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare this is not read-only but also not destructive, so the agent knows it has side effects; the description earns credit by quantifying them — 1 credit per still, free for scenes already rendered. It does not disclose whether stills are generated asynchronously (job id) or whether repeat calls are idempotent, which matters for a credit-spending tool.

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 tight sentences, front-loaded with what is produced and where it sits in the workflow, followed by the cost model. Nothing is padded or repeated from the schema.

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 two-parameter tool with no output schema, the description covers output content (one still per scene at the settled frame) and cost, which are the two things an agent most needs. It stops short of saying how stills are returned or whether the call is synchronous, a minor gap given no output schema exists.

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%, including the enum and the 9:16 default, so the schema carries the parameter load. The phrase 'in one size' does add one nuance — a single size applies uniformly to all stills rather than per-scene — but this is a small addition beyond the documented 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?

States a concrete verb-and-resource pair: it produces stills of every scene of a planned promo at the settled frame. The 'before rendering any clip' clause implicitly separates it from render_promo, and the resource (promo scenes) separates it from preview_graphic, but neither sibling is named outright.

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: 'before rendering any clip' signals this is a pre-render check. There is no explicit 'use preview_graphic for stills of a single graphic' or any when-not condition, so the agent must infer the routing from sibling names alone.

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