Skip to main content
Glama

storyshort_list_videos

List StoryShort videos with pagination and optional status filtering to find and track video generation progress.

Instructions

List your videos with optional pagination and status filter.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (1-100, default 20)
offsetNoPagination offset
statusNoFilter by status: PENDING, GENERATING_SCRIPT, GENERATING_VOICE, FETCHING_MEDIA, RENDERING, COMPLETED, FAILED

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it only implies a read-only, account-scoped listing. It omits sort order, what happens when offset exceeds the result count, whether pagination metadata is returned, and any rate-limit or auth context.

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?

A single front-loaded sentence with no filler; every clause carries information about scope or the available options.

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 straightforward, non-destructive list operation with rich schema documentation and zero required parameters, the core is covered. However, with no annotations and no output schema, the description should say more about ordering and the shape of results to be fully self-sufficient.

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 all three parameters (limit, offset, status) are fully documented with ranges, defaults and an enum in the schema itself. The description merely restates that these are optional pagination and filter inputs, adding no meaning beyond the schema.

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?

States a specific verb and resource ("List your videos") plus the two axes of control (pagination, status filter). It is clearly distinguishable in intent from storyshort_get_video and storyshort_generate_video, though it never names an alternative explicitly.

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 description makes clear you use it to enumerate videos and may narrow by status or page through results. There is no explicit when-to-use versus when-to-call storyshort_get_video, and no guidance on when a status filter is preferable to listing everything.

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