Skip to main content
Glama

Check a story video

get_story_video
Read-onlyIdempotent

Check an AI Story Video started with start_story_video: the step, the progress, the minutes left, the finished video link and (choose your path) the vote options for Part 2. With wait true the call waits up to 40 seconds for the next step. Without an id it lists the user's latest story videos.

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

Input Schema

NameRequiredDescriptionDefault
idNoThe story id from start_story_video
waitNoWait up to 40 seconds for the next step. Default false.
limitNoWithout an id: how many to list. Default 5.

Output Schema

NameRequiredDescriptionDefault
storyNo
storiesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description earns credit for the extra behavioral detail: the 40-second long-poll ceiling on wait and the fallback list behavior when no id is supplied. It stops short of saying what happens if the job is still running after 40 seconds or whether a failed job surfaces an error state.

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?

The result fields and the polling knob are front-loaded into two dense sentences with no filler. The parenthetical "(choose your path)" is slightly cryptic and the closing listing sentence sits a bit awkwardly at the end, 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?

This is a low-complexity polling tool with an output schema, so return values need no explanation and the description correctly skips them. Combined with full annotation coverage, all three parameters, and both operating modes accounted for, the definition is sufficient, with only the sibling-tool routing left ambiguous.

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%, and the description largely restates what the schema already documents (id comes from start_story_video, wait is a 40-second wait, limit applies without an id). It adds no format, default, or interaction detail beyond those structured fields, so the baseline of 3 applies.

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 uses a specific verb and resource ("Check an AI Story Video") and enumerates the returned state (step, progress, minutes left, video link, Part 2 vote options), which lets an agent predict the response. It also declares a second mode (listing the user's latest story videos when no id is given). It does not, however, distinguish itself from the sibling check_story_video, which reads as a near-duplicate by name.

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 concrete operating guidance: use wait=true to block up to 40 seconds for the next step, and omit the id to list recent videos instead of polling one. What's missing is any explicit routing against the sibling polling tools (check_story_video, check_legacy_story), so the agent must guess which checker applies to which story type.

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