Skip to main content
Glama

Get a video

autoshort_get_video
Read-onlyIdempotent

Retrieve a video's rendering status and details by ID to check completion, blocked reasons, playable URL, or errors.

Instructions

Get one video's status and details by id. While rendering, status is PENDING/GENERATING_*/RENDERING with estimatedCompletionTime. A PENDING video that cannot render returns blockedReason (e.g. INSUFFICIENT_CREDITS) with creditsNeeded, creditsAvailable and topUpUrl: stop polling and resolve it. COMPLETED returns a playable videoUrl; FAILED returns error. Free. Motion clips (autoshort_generate_motion_clip) also return motionClip{promptSent, seed, resolution, seconds, credits}, and on failure errorCode and creditsRefunded.

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

Input Schema

NameRequiredDescriptionDefault
idYesVideo id (a director draftId works too). Every create tool returns it as `id` (also as `videoId`).
videoIdNoAlias of `id`: the name the create tools use in their answer. Send either one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false and 'Free', so safety is covered. The description adds substantial behavioral context beyond that: the status state machine, estimatedCompletionTime, blockedReason with creditsNeeded/creditsAvailable/topUpUrl, and creditsRefunded on failure. However, it partially duplicates the cost/safety picture the annotations and sibling tooling already imply. Rich but overlapping coverage lands at a 3.

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?

Front-loaded with the core action, then status semantics, then failure paths. Information-dense with no filler, though several sentences are long and pack multiple distinct behaviors (blocked handling, motion clip extras) into single runs.

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 read-only getter with no output schema, the description carries the return-value burden well: it documents status values, videoUrl, error, blockedReason shape, and motion-clip-specific fields plus failure refunds. Minor gaps remain around what a COMPLETED video object contains beyond videoUrl, and pagination/history is irrelevant here.

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 schema itself explains that videoId is an alias and that draftIds work, so the description adds nothing about parameters. Baseline 3 for a fully documented two-parameter 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?

A specific verb+resource: 'Get one video's status and details by id.' It immediately tells the agent this is a single-item status lookup and names the sibling whose output shape it partly covers (autoshort_generate_motion_clip). It stops short of distinguishing itself from other lookups such as autoshort_get_draft, even though the schema notes a draftId is accepted.

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?

Gives real usage direction: poll while status is PENDING/GENERATING_*/RENDERING, and explicitly says to stop polling and resolve the blocked case rather than retrying. It lacks an explicit statement of when to prefer a different lookup tool, but the polling workflow guidance is concrete and actionable.

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