Skip to main content
Glama

Render a batch of UGC variants

autoshort_ugc_render_batch
Idempotent

Approves and renders up to 20 UGC video variants as one all-or-nothing reserved batch after preview approval, then poll the campaign for completion.

Instructions

Approve and render up to 20 variants. Call ONLY after the user approved the preview. Pricing: character portrait 1 credit; preview 1 credit only when a new start frame is generated; a variant with a new clip 102 credits; a re-caption (same setting + expression, different hook, reuses the clip) 1 credit. The whole batch is reserved in one step before anything is generated — all or nothing; a short balance returns 402 and charges nothing. variantIds approves drafts from autoshort_ugc_preview; variants adds new hooks (setting/expression default to the latest previewed variant's, so they become cheap re-captions of its clip; fromVariantId re-captions a rendered clip). A clip that cannot be made falls back to the still frame and its clip credits come back. Poll autoshort_ugc_get_campaign every 30 seconds.

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>"
    },
    "name": "autoshort_ugc_render_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
variantsNo
campaignIdYes
variantIdsNo
idempotencyKeyNoRetry-safe: the same key returns the first batch and charges 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?

Goes well beyond the annotations by disclosing the credit price of every unit of work, the all-or-nothing batch reservation, the 402-with-no-charge failure mode, and the clip-failure fallback that refunds clip credits. It does not say how long a batch takes or what the response contains, which keeps it short of a 5.

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-loads the action and the approval gate before the pricing detail, and every sentence carries a fact an agent needs. It is dense and runs long in a single block without line breaks, which slightly hurts scanability.

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

Completeness2/5

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

This is an aggregation of mistakes: Description hides the pricing, the all-or-nothing reservation semantics, the 402 error, the credit refunds and the polling cadence. It is good, but its incompleteness around result shape and per-batch timing is the weak point here.

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?

With only 25% schema description coverage the description carries the weight, and it does: it explains that variantIds approves drafts, that variants adds hooks whose setting/expression default to the latest previewed variant (making them cheap re-captions), and that fromVariantId re-captions a rendered clip. The enum values for setting/expression and the campaignId role are still left to the schema.

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 pair and resource ('Approve and render up to 20 variants') with an explicit cap, and implicitly separates the render step from the preview and polling siblings by naming both autoshort_ugc_preview and autoshort_ugc_get_campaign.

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

Usage Guidelines5/5

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

Gives a hard precondition ('Call ONLY after the user approved the preview'), tells the agent which sibling to poll and at what cadence, and explains which of variantIds / variants / fromVariantId to pick for each intent (approve drafts vs. add hooks vs. re-caption a rendered clip).

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