Skip to main content
Glama

Preview a UGC variant

autoshort_ugc_preview
Idempotent

Preview a single UGC variant’s scene 1—character, setting, gesture, and hook—before rendering. Returns a preview URL and draft variant ID so users can approve the still first.

Instructions

Preview ONE variant's scene 1 before rendering anything: the character in the chosen setting and gesture (expression = body language), with the hook laid out as the video will show it. Returns previewUrl and a variantId (a draft). 1 credit only when a new start frame has to be generated; otherwise free. Show the still to the user; render only after they approve.

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": {
      "campaignId": "<campaignId>",
      "hook": "<hook>"
    },
    "name": "autoshort_ugc_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
hookYes
settingNo
campaignIdYes
expressionNo
idempotencyKeyNoRetry-safe: a repeat with the same key returns the first answer (replayed: true) and creates nothing.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only declare safety/idempotency flags; the description adds substantive behavior the agent could not otherwise know: 1 credit charged only when a new start frame is generated (otherwise free), the output is a draft variant, and nothing is rendered at this stage. This is strong cost and side-effect disclosure, short of covering failure modes or what invalidates a draft.

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?

Front-loaded with the core action, then outputs, then cost, then the approval gate, which is a logical order with no filler. The colon-heavy construction is dense but every clause carries information; a small loss for being crammed into one paragraph.

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?

With no output schema, the description supplies the return shape and the cost model, which is what matters for a preview-then-approve tool. Gaps are minor: default behavior when setting or expression is omitted, and any precondition on campaignId.

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 only 20%, so the description must compensate, and it does: it ties hook to the on-screen layout, setting to the character's environment, and crucially explains that expression means body language, which makes enum values like 'tapping' and 'scroll' interpretable. campaignId's role is left implicit and idempotencyKey relies on its schema description.

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?

States a specific verb and resource: preview ONE variant's scene 1 before rendering anything. It spells out exactly what the preview contains (character in the chosen setting and gesture, hook laid out as the video will show it) and what comes back (previewUrl, variantId), which clearly separates it from rendering siblings.

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?

Gives a clear workflow: preview first, show the still to the user, render only after they approve. That is explicit when-to-use guidance. It does not name the render sibling that follows, so the agent must infer the pairing from the catalog rather than the text.

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