Skip to main content
Glama

Render an approved draft

autoshort_render_draft
Idempotent

Render an approved draft into a short video after user confirmation, charging estimated credits upfront and returning a new video ID to poll until completion.

Instructions

Render an approved draft. Call ONLY after the user has seen the draft and said yes. Charges the draft's estimatedCredits now (40 with the default voice), before any rendering work; refunded automatically if the render fails for good. Narration is read verbatim and each scene shows its visual; targetDuration is recorded as requested, and the video runs as long as its narration takes to read (any mismatch was in the draft's warnings). Retry-safe: a repeated call returns the first submission and charges nothing. A short balance returns 402 and keeps the draft. If the account has no credits and has not yet had its free first video, this renders that video instead of failing: watermarked, labelled AI-generated, up to 30 seconds, standard voice, one per account, subject to the day's availability. The answer carries the new video id (not the draft id): poll that one. Rendering is asynchronous: poll autoshort_get_video every 20-30 seconds until status is COMPLETED or FAILED. If get_video returns blockedReason, stop polling and act on it (e.g. top up credits).

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": {
      "draftId": "<draftId>"
    },
    "name": "autoshort_render_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
draftIdYes
idempotencyKeyNoOptional; recorded with the submission. The draft itself can only be rendered once.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.0

TDQS

A4.8/5.0
Behavior5/5

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

Far beyond the annotations: it discloses when credits are charged (40 with the default voice, up front), the automatic refund on permanent failure, retry-safe semantics, 402 behavior and its side effects, and the watermarked free-first-video path with its limits. The async lifecycle and the requirement to poll the returned video id rather than the draft id are spelled out, which the openWorldHint/idempotentHint annotations cannot convey.

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 precondition, then cost, then retry and failure semantics, then the free-video exception, then polling. No filler sentences, but the single dense block covering credit edge cases, the free-video exception, and polling could be broken for faster scanning.

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?

Covers everything an agent needs for a paid, asynchronous mutation with no output schema: cost and refund rules, idempotent retry, error codes, the free-tier exception, which id to poll, and how to terminate polling. Nothing material is left implicit.

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 50% schema coverage, draftId is undocumented in the schema, and the description compensates by establishing that the id refers to an approved draft and that the response carries a different video id. The idempotencyKey interaction is only partially covered: the description explains retry safety and the schema notes a draft renders once, but the description never says how a supplied key behaves versus a plain repeat call.

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 ('Render an approved draft') and immediately qualifies it with the approval precondition, which separates it from the direct-generation siblings like autoshort_generate_video. An agent can tell this is the draft-to-video step without opening any schema.

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 an explicit gate ('Call ONLY after the user has seen the draft and said yes'), names the follow-up tool and cadence ('poll autoshort_get_video every 20-30 seconds'), and specifies stop conditions for COMPLETED/FAILED and blockedReason. It even routes the no-credit case to a fallback rather than leaving the agent to improvise.

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