Skip to main content
Glama

storyshort_get_video

Retrieve a StoryShort video’s status and details by ID after generation to check progress, including credit-related failure reasons.

Instructions

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "storyshort_get_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesVideo ID returned from generate

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full disclosure burden and does unusually well: it names a specific terminal failure mode, the exact field values returned (blockedReason INSUFFICIENT_CREDITS, creditsNeeded, creditsAvailable, topUpUrl), and states the operation will not be retried. It does not cover remaining behavior such as whether polling is rate-limited or what a successful status payload looks like.

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

Conciseness5/5

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

Three short sentences, no padding, and the core action is front-loaded ahead of the edge-case detail. Every sentence earns its place, including the credits-failure note, which is non-obvious.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read with no output schema, the description should cover the return shape, but it only documents the insufficient-credits branch and leaves the shape of a normal response (status values, detail fields) unstated. It is adequate for the failure path but incomplete for the success path.

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 coverage is 100% and the single parameter is documented as "Video ID returned from generate." The description adds only the phrase "by ID," which is redundant with the schema, so the baseline 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?

"Get video status and details by ID" gives a concrete verb (get), resource (video), and scope (status + details, by ID). It is distinguishable from storyshort_list_videos and storyshort_generate_video by the single-ID lookup framing, though it never names a sibling explicitly.

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?

"Use after generating to check progress" gives clear situational guidance for the primary use case (polling a generation job). It stops short of explicit exclusions — e.g. when to call list_videos or generate_video instead — so it falls short of the top band.

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