Skip to main content
Glama

Get a video

get_video
Read-onlyIdempotent

Get the status and details of one video the caller owns, by id. While rendering, status is PENDING/GENERATING_*/RENDERING and estimatedCompletionTime (seconds) is returned. When status is COMPLETED, a playable videoUrl and thumbnailUrl are returned; when FAILED, error says why, and a failure for lack of credits adds blockedReason "INSUFFICIENT_CREDITS" with creditsNeeded, creditsAvailable and topUpUrl (it will not be retried: top up and create the video again). Requires the "video:read" scope. Read-only, never charges credits. Also polls a motion clip made by generate_motion_clip: the answer then has kind "motion_clip", the promptSent, and on FAILED an 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": "get_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe video id returned by create_video or list_videos.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the readOnly/destructive annotations: requires the 'video:read' scope, never charges credits, and documents the full status lifecycle plus what is returned at each state. The INSUFFICIENT_CREDITS branch is especially valuable because it discloses that the job will NOT be retried and that the user must top up and recreate — non-obvious behavior an agent could otherwise get wrong.

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 purpose, then status branches in a logical order, with no filler sentences. It is dense and long-ish for one tool, but each clause carries distinct behavioral information.

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

Completeness5/5

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

There is no output schema, so the description carries the full burden of describing return values — and it does, covering PENDING/GENERATING/RENDERING, COMPLETED urls, FAILED error and credits fields, and the motion-clip variant. Nothing an agent needs to interpret a response is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only one parameter and the schema already documents it at 100% coverage (id from create_video or list_videos), so the baseline is high. The description adds the ownership constraint ('one video the caller owns'), which is meaning the schema does not convey.

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+resource: 'Get the status and details of one video the caller owns, by id,' which distinguishes it from list_videos and from the creation siblings. It even extends the scope to motion clips, so an agent knows the same tool serves both asset kinds.

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?

Implies the polling pattern clearly ('While rendering...', 'Also polls a motion clip made by generate_motion_clip'), which tells the agent when to call it repeatedly. It lacks an explicit 'use list_videos instead when you don't have an id' statement, so it stops short of full alternative routing.

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