Skip to main content
Glama

Get a video

get_video
Read-onlyIdempotent

One video: status (queued → downloading → running → ready | failed), seconds left, and when ready a result_url to download. Poll every 15–30 s after start_swap, use_own_video or stitch_videos.

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_idYes

Output Schema

NameRequiredDescriptionDefault
idYes
statusYes
app_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Beyond the read-only/idempotent annotations, the description discloses the status lifecycle, seconds-left progress, availability of result_url, and polling cadence. This gives the agent meaningful operational context for a polling read tool.

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?

The description is two compact sentences with no wasted wording. Purpose and polling guidance are front-loaded, and the status states are summarized efficiently.

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 one-parameter read tool with an output schema and rich annotations, this is nearly complete: it explains purpose, return timing, status flow, and polling behavior. The main missing piece is video_id semantics, which matters slightly more because the schema does not describe it.

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

Parameters2/5

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

The schema has 0% description coverage and the description does not explain the sole video_id parameter, such as where it comes from or what it identifies. It only implies that the tool operates on one video, leaving the parameter's meaning carried almost entirely by the schema pattern.

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?

The description clearly identifies the resource as a single video and specifies the key returned data: status, seconds left, and result_url when ready. It distinguishes this from list-style siblings, though it uses a noun phrase rather than an explicit verb.

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?

It gives concrete when-to-use guidance by naming the operations after which to poll (start_swap, use_own_video, stitch_videos) and recommends a 15–30 s cadence. It does not explicitly state when not to use it or name alternatives such as list_videos for browsing.

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.