Skip to main content
Glama

List video templates

autoshort_list_templates
Read-onlyIdempotent

Lists ready-made video, motion clip, and episode templates with prompts, prices, and generation arguments so users can browse or filter by kind, genre, niche, or ID before creating content.

Instructions

List 12 ready-made video templates (kind "video": history facts, scary stories, motivation, personal finance education, kids music, product ad, small-business explainer, character mini-episode and more) and 26 AI motion clip templates (kind "motion": single-shot prompts for landscapes, macro food, animals, products, abstract loops, city nights, weather, miniatures, fantasy scenery and short-drama beats in thriller, comedy, horror, romance, action, epic and drama; the clips are silent, and any person is only a silhouette, seen from behind or as hands, never a face or a child). A video template has the full prompt, length, credit price and the exact arguments for autoshort_generate_chat_video. A motion template has the full prompt, genre, a six-slot breakdown (camera, subject, action, setting, style, lighting: each phrase is literally in the prompt), a one-line why, seconds, credits, a demoVideoUrl when a sample clip exists, and the arguments for autoshort_generate_motion_clip (pass its id as templateId, or edit the prompt and pass it as prompt). 6 short-drama episode scripts (kind "episode", 12-60 s multi-shot episodes for Character Studio; listed only with kind "episode" or an id) carry a script, logline and cliffhanger. An episode is only made as one of the episodes of a reviewed, confirmed season plan: add it to a plan with autoshort_save_season_plan (at least 3 episodes, the cast, the narrator voice and the style), review and confirm it, then autoshort_quote_character_episode prices it for free. Edit any prompt first (swap the topic, shop name or facts). Pass kind "video", "motion" or "episode", id for one template, genre (drama, thriller, comedy, horror, romance, action, epic, nature, product, fantasy) to filter motion and episode templates, or niche (video templates) to filter. Nothing is created or charged; show the user the price before you generate. Free.

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_list_templates"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoReturn just this template.
kindNovideo = Chat to Video templates, motion = AI motion clip templates, episode = short-drama scripts for a season plan (autoshort_save_season_plan; only returned when asked for with kind "episode" or id). Default: video and motion.
genreNoOnly motion and episode templates of this genre (episode scripts exist for drama, thriller, comedy, horror and romance).
nicheNoOnly templates for this niche (see autoshort_list_niches).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.0

TDQS

A4.2/5.0
Behavior5/5

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

Goes well beyond the annotations (which already declare readOnly/idempotent): it discloses that nothing is created or charged, that the price must be shown before generating, the exact field inventory returned per template kind (prompt, length, credits, six-slot breakdown, demoVideoUrl, script/logline/cliffhanger), and the non-obvious filtering quirk for episodes. These are real behavioral facts an agent could not infer from 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.

Conciseness3/5

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

Purpose is front-loaded, but the body is one dense paragraph stuffed with long parenthetical motif lists ("landscapes, macro food, animals, products, abstract loops ...") and the silhouette/child content aside. Much of that enumeration does little to help selection and could be trimmed or split into per-kind sentences.

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?

With no output schema, the description takes on the job of describing return fields and does so thoroughly, plus the episode-to-season-plan workflow. Only minor gaps remain, such as whether the listing is truncated or ordered, which is unlikely to block a correct call.

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 the schema already documents id, kind, genre and niche — including the genre/enum constraints for episodes. The description mostly restates these semantics rather than adding new ones; the only extra value is explaining how returned ids feed into generation tools, which is about other tools rather than these parameters.

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 ("List 12 ready-made video templates ... and 26 AI motion clip templates ... 6 short-drama episode scripts") and enumerates exactly what each kind contains. An agent can immediately tell this is a read-only catalog tool, distinct from autoshort_list_videos (produced videos) or autoshort_list_niches.

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?

Clear call-side guidance: pass kind, id, genre or niche, and the hidden default (episodes only returned with kind "episode" or an id). It also routes downstream usage ("Edit any prompt first", use the args for autoshort_generate_chat_video / autoshort_generate_motion_clip) and points at autoshort_list_niches for niche values. No explicit comparison to autoshort_list_options or autoshort_list_series, so not a full when/when-not treatment.

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