Skip to main content
Glama
Sign In

AutoShort

by org.autoshort
OverviewDiscussionsAdmin

autoshort_generate_video

Idempotent

Generate a video from a topic; AutoShort writes the script (to render a script you already agreed with the user, use autoshort_draft_video). Optional image_urls (public https links, up to 6) put the user's own pictures in the first scenes. Costs 65 credits (40 render + 25 ElevenLabs voice); art style does not change the price. Images do not change the price. A short balance is refused with 402 INSUFFICIENT_CREDITS. 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: this makes a narrated video of still images from a topic. If the user pasted a cinematic / video-model prompt, use autoshort_generate_motion_clip instead.

Input Schema

NameRequiredDescriptionDefault
nicheNoOptional content niche; see autoshort_list_niches.
topicYesWhat the video is about: one named subject, one angle, one twist. Short topics still work. e.g. "Why airplane windows have a tiny hole in them".
qualityNoOutput resolution. Omit for the plan's resolution; asking for more than the plan renders returns 403 QUALITY_NOT_IN_PLAN.
artStyleNoOptional art style; default AUTOSHORTS.
durationNoTarget length in seconds (default 30). 15/30/60/90 = multi-scene faceless video; 5 and 8 make a very short video on the same pipeline and price.
languageNoOptional BCP-47 code (e.g. "en", "vi"). Defaults to "auto".
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.
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 observed

TDQS

A4.7/5.0
Behavior5/5

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

With annotations present the bar is lower, yet the description still discloses the credit cost breakdown (65 = 40 render + 25 voice), that art style and images do not change price, the 402 INSUFFICIENT_CREDITS refusal, and the asynchronous render contract including the 20-30s polling cadence and how to handle blockedReason. That is substantially more than the annotations 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 purpose, then cost, then async contract, then an explicit ROUTING block — a well-ordered structure where nearly every sentence carries decision-relevant information. It is dense and the price facts are stated twice in slightly different form, which keeps it from a 5.

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?

For an 8-parameter, paid, asynchronous mutation with no output schema, the description covers cost, failure modes, polling lifecycle, and routing. It stops short of describing the success payload beyond the status field, so an agent still learns the result shape only by calling autoshort_get_video.

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 100%, so a baseline of 3 applies, but the description adds real meaning for image_urls: positional scene mapping, download/strip-EXIF/re-host behavior, hourly quotas, and that excess images are refused rather than dropped. It does not add anything for niche, quality, language, or idempotencyKey beyond the schema, so it stops short of 5.

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?

Opens with a specific verb+resource ("Generate a video from a topic") and immediately distinguishes itself from autoshort_draft_video, which renders an already-agreed script. The ROUTING sentence further separates it from autoshort_generate_motion_clip, so an agent can pick the right sibling 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 explicit when-to-use (topic-driven narrated still-image video), explicit alternatives with their selecting conditions (draft_video for an approved script, generate_motion_clip for a pasted cinematic prompt), and even names the follow-up tool (autoshort_get_video). Both the positive and the negative routing cases are covered.

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

All AutoShort toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources