Skip to main content
Glama

storyshort_generate_video

Generate an AI short video from a topic, niche, art style, duration, and quality. Returns a video ID to poll for completion status.

Instructions

Generate an AI video from a topic. Returns a video ID for status polling. Costs 40 credits with the default voice; art style does not change the price. The request is refused with 402 INSUFFICIENT_CREDITS (credits needed, available, top-up URL) when the balance is short. Rendering is asynchronous: poll storyshort_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": {
      "topic": "<topic>"
    },
    "name": "storyshort_generate_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
nicheNoVideo niche (e.g., MOTIVATIONAL, AI_FACTS, SCARY_STORIES); see storyshort_list_niches
topicYesVideo topic or script idea
qualityNoOutput resolution. Omit to use the plan's resolution. Asking for one the plan does not render returns 403 QUALITY_NOT_IN_PLAN.
artStyleNoArt style id (e.g., AUTOSHORTS, COMIC_BOOK, PIXEL_ART); legacy ids LEGO, DISNEY_TOON, STUDIO_GHIBLI are shown as Brick Toy, Storybook Cartoon, Hand-drawn Anime. See storyshort_list_niches
durationNoTarget duration in seconds: 30, 60, or 90

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full behavioral burden and does well: it discloses the 40-credit cost, that art style does not affect price, the 402 INSUFFICIENT_CREDITS refusal with its payload fields, and that rendering is asynchronous. It stops short of stating authentication or plan requirements beyond the credit/quality constraints documented in the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Five short sentences, front-loaded with purpose and return value, then cost, then the async polling protocol and its stop condition. No filler and no repetition of schema content.

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?

Without an output schema, the description still explains that a video ID is returned and enumerates the terminal statuses and blockedReason behavior, which is what an agent needs to chain calls correctly. A brief note on what the generate response contains beyond the ID is the only minor gap.

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

Parameters3/5

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

Schema description coverage is 100%, so every parameter already has meaningful documentation including enums and error behavior (403 QUALITY_NOT_IN_PLAN). The description adds only the pricing nuance tied to the default voice rather than per-parameter meaning, so baseline 3 applies.

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 description opens with a specific verb and resource ('Generate an AI video from a topic') and immediately states the return value (a video ID for polling), which cleanly separates it from the sibling read/poll tools like storyshort_get_video and storyshort_list_niches referenced in the schema.

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

Usage Guidelines4/5

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

It gives explicit downstream workflow guidance: poll storyshort_get_video every 20-30 seconds until COMPLETED or FAILED, and stop polling if blockedReason is returned. What it lacks is any statement of when not to call it (e.g. prerequisites or preconditions for generating), which keeps it from a 5.

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