Skip to main content
Glama

How to write a faceless story video

story_video_guide
Read-onlyIdempotent

AI Story Video: faceless narrated short videos for TikTok, Reels and Shorts in many formats: 'what if' explainers, body facts, history, scary stories, space, animals, how it works, mysteries, survival, myths, POV, storytime, would you rather, psychology, rise and fall, disasters, Bible stories, build it, cartoon stories and choose-your-path episodes. One narrator voice over AI pictures and clips, with captions and music. This returns every format with examples, the options with prices, and the exact prompts MakeViral's own writer gets for this format and length. You can write the whole script yourself (any model, in the user's own way) and pass it to check_story_video and start_story_video as draft; then MakeViral does not write it and does not charge for writing it. Without a script, start_story_video writes it from the idea.

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": "story_video_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
ideaNoOne line, e.g. 'What if the moon disappeared?'
paceNo
musicNo
storyNoThe user's own full story, when there is one: the script keeps its events, names and facts
styleNoArt style. Default: the format's.
aspectNoDefault 9:16 (TikTok, Reels, Shorts).
formatNoThe video format. Default what-if. story_video_guide lists them with examples.
qualityNoHow many scenes move (AI clips) instead of stills. Default: the format's.
secondsNoLength in seconds. Default: the format's.
voiceIdNoNarrator voice id (story_video_guide). Default: the format's.
captionsNoCaption style. Default: the format's.
languageNoNarration language. Default en.
continueFromNoPart 2 of a finished choose-your-path (or 'Part 2?') story of this user

Output Schema

NameRequiredDescriptionDefault
guideYes
choicesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), but the description adds genuinely useful behavior: it returns pricing, exposes the exact internal writer prompts, and discloses the billing rule that scripting it yourself avoids the writing charge. That is real context beyond structured fields.

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

Conciseness2/5

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

The first sentence enumerates roughly twenty formats in prose, which duplicates the `format` enum already in the schema and dilutes the front of the description. The genuinely valuable content — return payload, pricing, and the self-written-script workflow — only appears after that redundant listing, so the text is neither front-loaded nor fully earning its length.

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?

For a read-only reference tool with an output schema, the description says what comes back (formats with examples, priced options, exact prompts) and how its output feeds the sibling create/check tools, so an agent can act without guessing. The remaining details live in the output schema and the well-covered input schema.

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 85% and 9 of 13 parameters are enums with inline descriptions, so the schema carries the parameter burden and the baseline of 3 applies. The description adds little per-parameter meaning, and it introduces a naming mismatch by calling the user-supplied script `draft` when this tool's own parameter is `story`.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description does state a concrete verb+resource — 'This returns every format with examples, the options with prices, and the exact prompts' — and it names check_story_video and start_story_video, so an agent can place it in the workflow. However, that sentence is buried mid-paragraph behind a product blurb, and the opening line describes the video product rather than the tool itself.

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

Usage Guidelines3/5

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

Usage is only implied: the schema hints ('story_video_guide lists them with examples', 'voiceId (story_video_guide)') plus the mention of passing your own script to check_story_video and start_story_video as `draft` suggest this is the reference to consult before starting. There is no explicit 'call this first when you need formats/prices/prompts' or any statement of when NOT to use it.

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.

Resources