Skip to main content
Glama

Check a story video and its price

check_story_video
Read-onlyIdempotent

Check an AI Story Video before it is made, without any charge: the exact price in credits, and (with your own draft) the script as it will be made, checked and cleaned. A script must have exactly the scene count of its length and fit the length when read aloud. Send the same input you will send to start_story_video.

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

Input Schema

NameRequiredDescriptionDefault
ideaNoOne line, e.g. 'What if the moon disappeared?'
paceNo
draftNoYour own script: the JSON the writer prompt of story_video_guide asks for (title, characters, places, scenes, choices, stats...).
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
draftNo
scenesYes
creditsYes
writerIncludedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered; the description adds the material fact that the call is free of charge and that it performs validation (scene count must match length, script must fit the length when read aloud). It does not describe response shape, but an output schema exists.

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?

Two sentences, front-loaded with the core benefit (free pre-check plus price) before the draft caveat and the input-parity instruction. Phrasing like 'checked and cleaned' is slightly loose but nothing is wasted.

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 a 14-parameter tool with nested draft objects and an output schema, the description covers the essential contract: it is a free dry run, it returns price, and it validates the script. Return-value details are delegated to the output schema, which is acceptable.

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 86%, so the baseline is 3, and the description adds real meaning by explaining that `draft` is the user's own script and that the whole input must mirror what start_story_video will receive. The validation rules about scene count and read-aloud length further clarify what values are acceptable.

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: check an AI story video before creation, returning the exact price in credits and, when a draft is supplied, the normalized script. This clearly separates it from start_story_video, which actually produces the video.

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?

Explicitly says to send the same input that will later go to start_story_video, which frames this as a pre-flight dry run, and notes the no-charge aspect that motivates using it first. It does not spell out when to skip the check, so it stops short of full when/when-not guidance.

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