Skip to main content
Glama

List videos

autoshort_list_videos
Read-onlyIdempotent

List your videos newest first with pagination and an optional status filter to review and track generation progress across pending, completed, failed, or draft items.

Instructions

List your videos, newest first, with pagination and an optional status filter (PENDING, GENERATING_SCRIPT, GENERATING_VOICE, FETCHING_MEDIA, RENDERING, COMPLETED, FAILED, DRAFT). Free.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 20).
offsetNoPagination offset (default 0).
statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description still adds real value on top: deterministic newest-first ordering, pagination via limit/offset, a status filter covering the full lifecycle, and "Free" indicating no credit consumption. It stops short of stating result shape or rate limits, hence not a 5.

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?

A single front-loaded sentence with no filler: subject, ordering, paging, filter, cost. The inline enum listing is long but functional; the trailing "Free." is terse and earns its place as a cost hint.

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 simple zero-required-parameter read tool with annotations covering safety, this is close to self-sufficient. The remaining gap is that nothing describes what each returned video object carries (no output schema exists), which would help an agent decide whether to page through results or fetch a specific video afterward.

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 67% and the schema already documents limit (default 20, max 100) and offset (default 0), while the description merely restates "pagination." The status enumeration is repeated verbatim from the schema's enum, so the description adds little meaning beyond the structured fields apart from confirming that the sort order interacts with offset paging.

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 ("List your videos") plus the result ordering ("newest first"), which is exactly what an agent needs to distinguish it from sibling list tools such as autoshort_list_series or autoshort_list_templates.

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 implied by "List your videos" with an optional status filter, so an agent can infer this is the read/browse path for generated videos. However, it names no alternatives and gives no explicit when-not-to-use guidance (e.g., use autoshort_get_draft for an unfinished video, or autoshort_cancel_video to stop a running render).

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