Skip to main content
Glama

Draft a video (free, no render)

autoshort_draft_video

Create a free video draft scene by scene from an agreed script, so you can review scenes, length and estimated credits before rendering and charging credits.

Instructions

Create a video DRAFT — nothing is rendered and no credits are charged. Director mode, the recommended way to make a video the user has opinions about: (1) write and agree the script with the user in this conversation first — narration per scene and what each scene should show; (2) call autoshort_draft_video with scenes[] (free, nothing is rendered or charged); (3) show the user the draft (scenes, estimated length, estimated credits, warnings) and apply their changes with autoshort_update_draft; (4) only after the user approves, call autoshort_render_draft — that is when credits are charged. Narration is read VERBATIM: AutoShort never rewrites it. Each scene with a visual gets exactly that image (plus the art style). A scene can carry image_url (the user's own picture, public https link): that scene shows it instead of a generated image, and the draft marks it imageSource "your image". Pass scenes[] for a script you agreed with the user (free; stored word for word), or a brief to have AutoShort write one draft for review (needs a positive credit balance, max 20 per hour). Returns draftId, the scenes, estimatedDurationSeconds, estimatedCredits and warnings[].

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "autoshort_draft_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
briefNoOnly when there is no agreed script: what the video should be about. With scenes[] it is used as context for auto images.
titleNoHeadline shown over the first 1.5s and used as the video title. Defaults to the first sentence.
scenesNoThe agreed script, scene by scene, in order.
artStyleNoVisual style; see autoshort_list_niches. Default AUTOSHORTS (cinematic photography).
languageNoBCP-47 narration language ("en", "vi", …). Omit to detect it from the narration.
aspectRatioNo
targetDurationNoRequested length in seconds. Kept as requested — if the verbatim narration cannot fit it, warnings[] says so with a word count that would.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.0

TDQS

A4.6/5.0
Behavior4/5

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

Adds substantial behavior beyond the annotations: no rendering or charges on draft creation, verbatim narration that AutoShort never rewrites, image_url precedence with imageSource "your image" marking, and a rate limit plus positive-balance requirement for brief mode. Minor gap: it doesn't say what happens to a draft's lifetime or whether drafts can be re-drafted repeatedly against the 20/hour limit.

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 single most decision-relevant fact (free, nothing rendered) before the numbered workflow. The workflow and verbatim-narration notes all earn their place, though the piece is long enough that some scene-level detail could be trimmed.

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 creation, the approval gate before spending credits, the two input modes, and the return payload (draftId, scenes, estimatedDurationSeconds, estimatedCredits, warnings[]) despite no output schema. An agent has enough to call it correctly and to know what happens next.

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 high (86%), so the baseline is 3, but the description adds real meaning: brief is only for when there is no agreed script and doubles as context for auto images, scenes[] are stored word for word, and image_url replaces a generated image in that scene. artStyle, language and aspectRatio are left entirely 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 and resource ('Create a video DRAFT') and immediately bounds it: 'nothing is rendered and no credits are charged.' It explicitly contrasts with autoshort_render_draft (where credits are charged) and autoshort_update_draft, so an agent can route without opening a 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 four-step workflow: agree the script first, draft with scenes[], show the user and revise via autoshort_update_draft, and only call autoshort_render_draft after approval. It also names the alternative input mode (brief vs scenes[]) with the condition that selects it.

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