Skip to main content
Glama

get_video_status

Read-only

Check a video generation job's status and wait up to 60 seconds for completion, returning a saved file path when finished; call again while queued, running, or downloading.

Instructions

작업 상태를 확인한다. 과금되지 않는다.

    완료될 때까지 최대 wait_seconds(상한 60초) 동안 기다린다.
    status 가 queued/running/downloading 이면 이 도구를 다시 부른다.
    succeeded 이면 file 에 저장된 영상 경로가 있다.
    

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": {
      "job_id": "<job_id>"
    },
    "name": "get_video_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes
wait_secondsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint=false, but the description adds genuinely new behavior: no billing, a blocking wait capped at 60 seconds, and the meaning of the file field on success. It does not describe what happens on failure or what the returned status values beyond the listed ones mean, which keeps it at a 4.

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?

Four short lines, front-loaded with the purpose and the no-charge fact, then the wait behavior and the status-based branching. Every sentence carries actionable information with no filler.

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?

With an output schema and annotations already supplied, the description covers cost, blocking wait limits, the polling loop, and the success payload field. The remaining gap is handling of failure or unexpected status values, which an agent polling a job would want to know.

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?

Schema coverage is 0% and parameter titles are bare, so the description must carry the load. It does explain wait_seconds meaningfully, including the max-wait behavior and the 60-second cap that the schema does not state (schema only shows default 30). job_id is left to its self-evident name, but the key parameter is well-covered.

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?

States a specific verb and resource (check job status) and distinguishes itself from siblings implicitly by being the polling tool rather than the generation or download tool. It does not name a sibling, so it stops short of a 5, but an agent can tell what it is for.

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 explicit re-call guidance: if status is queued/running/downloading, call this tool again, and if succeeded the path is in file. This is a clear when-to-call rule. The gap is terminal failure states (failed/error) and when to stop polling, which are not covered.

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