Skip to main content
Glama

autoshort_generate_chat_video

Idempotent

Create a video from a natural-language creative brief; AutoShort writes the script from it. To keep an agreed script word for word with your own shots, use autoshort_draft_video instead. To use the user's own pictures ("make a video with these images"), pass image_urls (public https links, up to 6): image 1 becomes scene 1, image 2 scene 2, …; the rest are generated. Naming an image inside the brief does NOT attach it: only image_urls do. If the brief points at a picture you did not pass, the answer carries warnings["IMAGE_IGNORED"] with a warningText (read it to the user), or CHAT_NO_IMAGE_INPUT (retry with image_urls, or proceedWithoutImage: true). Optional captionSecondaryLanguage adds a translated second caption line under the narration captions (e.g. "vi" for English narration with Vietnamese under it); "none" turns it off for this video even if the account default has one; omitted = the account default (off unless the user set one). It costs nothing extra. Costs 40 credits with the default voice (+25 if ElevenLabs narrates); images do not change the price. 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). ROUTING: if the user pasted a cinematic / video-model prompt (camera, lens, lighting, a scene description), do NOT use this tool: it writes its own script and makes narrated still-image scenes. Use autoshort_generate_motion_clip, which sends the prompt as written. Use this tool for narrated stories and facts. videoProvider VEO_3_1_OPERATOR is operator-fulfilled and not guaranteed: it does not turn a prompt into a moving clip.

Input Schema

NameRequiredDescriptionDefault
messageYesCreative brief describing the desired video.
artStyleNoArt style returned by autoshort_list_niches.
languageNoNarration language. Omit to detect it from the brief.
image_urlsNoOptional. The user's OWN images to use as the first scenes: image 1 = scene 1, image 2 = scene 2, and so on; the remaining scenes are generated as usual. https URLs only, up to 6 per call, JPEG/PNG/WebP, each at most 10 MB and 25 megapixels; at most 30 images per hour per account. Animated WebP uses its first frame; GIF and SVG are rejected. AutoShort downloads each image once, strips EXIF/GPS, re-encodes it and serves it from its own domain (your URL is never linked into the video). Fast (FFMPEG) multi-scene videos only. The answer states how many images were used and for which scenes; more images than scenes is refused, never silently dropped. Only send images the user owns or may use; each is shown as a still with a slow zoom and is never animated or used to generate a person.
aspectRatioNo
videoProviderNoFFMPEG for fast multi-scene video; VEO_3_1_OPERATOR for cinematic quality when eligible.
idempotencyKeyNoRetry-safe: a repeat with the same key returns the first answer (replayed: true) and creates nothing.
targetDurationNoLength in seconds. With image_urls and no targetDuration, 30 is used (6 scenes) so every image has a scene.
proceedWithoutImageNoSet true to create the video from the text even though the brief points at an image you did not pass in image_urls. Without it, a brief that clearly hands over a file ("the photo I attached", an image URL) is refused with CHAT_NO_IMAGE_INPUT before anything is charged; a softer mention creates the video and returns warnings: ["IMAGE_IGNORED"] + warningText.
captionSecondaryLanguageNoSecond caption line language (translated, shown under the narration captions). "none" = no second line for this video. Omit to use the account default. Same language as the narration = ignored.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Goes well beyond the annotations (which only say non-read-only, open-world, idempotent, non-destructive): it discloses exact credit cost (40, +25 for ElevenLabs), that images don't change price, that rendering is asynchronous with a 20-30s polling loop against autoshort_get_video, and that polling must stop on blockedReason. It also enumerates the two failure modes (IMAGE_IGNORED warning vs CHAT_NO_IMAGE_INPUT refusal before charging), which is precisely the kind of mutation-and-side-effect context an agent needs.

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 purpose, then alternatives, then parameters, then routing — a sensible order with no filler sentences and every claim carrying operational weight. It is long and dense for a 10-parameter tool, and the routing block arguably belongs earlier, but nothing is genuinely wasted.

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?

With no output schema, the description compensates by describing return signals: status values COMPLETED/FAILED, blockedReason, warnings["IMAGE_IGNORED"] with warningText, replayed: true for idempotent retries, and scene counts for images. For an async, credit-charging, open-world generator this covers everything an agent needs to call it and handle the response.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 90%, yet the description still adds meaning the schema cannot: image_urls are positional (image 1 = scene 1) and are the ONLY way to attach images — 'Naming an image inside the brief does NOT attach it'. It also explains captionSecondaryLanguage's 'none' vs omitted (= account default) semantics and the 30s/6-scene default for targetDuration. Only aspectRatio is left uncovered, a minor omission.

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?

The opening states a specific verb and resource — 'Create a video from a natural-language creative brief' — and immediately discloses the key mechanic (AutoShort writes the script). It then distinguishes itself from the two nearest siblings, autoshort_draft_video (verbatim script) and autoshort_generate_motion_clip (as-written prompts), so an agent can route without opening schemas.

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?

Explicit positive and negative routing: use this for 'narrated stories and facts', use draft_video for word-for-word scripts with own shots, and a dedicated ROUTING paragraph excluding cinematic/video-model prompts in favour of autoshort_generate_motion_clip. It also names preconditions (VEO_3_1_OPERATOR eligibility) and a fallback path (proceedWithoutImage: true).

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.