StoryShort
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| STORYSHORT_API_KEY | Yes | StoryShort API key (sk_live_...) set as an environment variable for the local stdio server. Without an API key the server still starts and answers tools/list, but every tool call is refused until a key is set. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| storyshort_generate_videoA | 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). |
| storyshort_get_videoA | Get video status and details by ID. Use after generating to check progress. A video that failed for lack of credits returns blockedReason INSUFFICIENT_CREDITS with creditsNeeded, creditsAvailable and topUpUrl: it will not be retried. |
| storyshort_list_videosB | List your videos with optional pagination and status filter. |
| storyshort_list_nichesA | List available video niches, art styles, video qualities, and duration options for video generation. |
| storyshort_get_credit_balanceA | Check your current credit balance, monthly allocation, bonus credits, and plan tier. |
| storyshort_get_usage_statsA | Get API usage statistics: credit balance, API call counts (today/total), and recent credit transactions. |
| storyshort_get_subscriptionA | Check your subscription plan, status, video limits, and credit allocation. |
| storyshort_list_api_keysA | List your API keys with prefix, scopes, rate limits, and usage stats. Note: only key prefixes shown, never full secrets. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| generate_video | Step-by-step guide to generate an AI video with StoryShort |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| credit-balance | Current credit balance, monthly allocation, and plan tier |
| rate-limit | Current API rate limit status from most recent request |
TDQS
Scored across 8 tools
The generate/poll/list video tools are clearly distinct, but three read tools overlap on billing information: get_credit_balance, get_subscription, and get_usage_stats all report credits/plan/allocation, so an agent asking 'how many credits do I have?' or 'what's my plan?' could reasonably land on any of them. Descriptions help somewhat but the boundaries are not clean.
Every tool follows the same storyshort_<verb>_<noun> pattern (get_credit_balance, get_subscription, generate_video, get_video, list_videos, list_niches, list_api_keys, get_usage_stats) with no camelCase or mixed-verb deviations.
Eight tools is well-scoped for a video-generation API: one generation action, one polling action, three list/introspection tools, and three account tools. Nothing feels padded or missing at the count level.
The core lifecycle (discover niches/options, generate, poll status, list past videos) plus billing introspection is covered end to end. Minor gaps remain: no delete/cancel for videos and API keys are list-only (no create or revoke), presumably pushed to the dashboard.