Skip to main content
Glama

Get a video

get_video
Read-onlyIdempotent

Status, progress, credits and, when completed, the download links status is queued, processing, completed, failed or cancelled. While it waits, queue says why: plan_limit (the organization already makes as many videos at once as its plan allows; position is its place in line) or render_capacity (every render machine is busy; estimated_wait_seconds is about how long). Completed videos have outputs with download_url (full quality), web_url (720p) and poster_url, signed for 7 days. A lyric video's poster is a frame with one whole lyric line on screen (the hook when it can be), ready to set as the thumbnail where you post it; a Canvas's is its first frame; a music video's a frame of its first seconds. poster_seconds says where in that file the poster was cut, for posts that take a cover frame offset instead of an image (TikTok); null on videos made before it was kept. Failed videos have error and error_code; AI_VIDEO_UNAVAILABLE means the AI video couldn’t be made for a reason on our side, so make it again later.

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": {
      "video_id": "<video_id>"
    },
    "name": "get_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
video_idYesThe video id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior5/5

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

With annotations covering read-only/idempotent, the description goes well beyond them: signed download/web/poster URLs valid 7 days, queue reason semantics for plan_limit vs render_capacity, poster frame semantics per video type, poster_seconds offset behavior and its null back-compat case, and the meaning of AI_VIDEO_UNAVAILABLE with a retry recommendation. That is exactly the behavioral context an agent cannot get from structured fields.

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

Conciseness3/5

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

Dense but not padded – nearly every clause carries real semantics about returned fields. However it is one run-on blob with a broken opening sentence, and the most important information (what the tool does) is not front-loaded, so structure works against it.

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?

There is no output schema, so the description must carry return-value meaning, and it does thoroughly for statuses, URLs, posters, and errors. It still omits the general shape of the response (identity/other fields) and error behavior for an unknown id, so it is strong but not exhaustive.

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 video_id parameter is documented in the schema, but the description adds nothing about format, where the id comes from, or invalid-id behavior. Baseline 3 for a fully-covered single-param schema is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description enumerates what comes back (status, progress, credits, download links) which implies retrieval of a video record, but it never states the action plainly and never distinguishes itself from siblings like show_video, wait_for_video, or list_videos. The opening sentence is also garbled ('...the download links status is queued...'), so the purpose must be inferred from the title and name rather than read.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It describes the queue/polling state but gives no explicit instruction on when to call get_video versus wait_for_video or show_video, and no exclusion or prerequisite. The only actionable hint is buried ('While it waits') and is about interpreting a queue reason, not about choosing the tool.

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