Skip to main content
Glama

get_job_status

Check the status of an Epic Video generation job by its job id. Returns the status (queued, rendering, upscaling, done, or failed) and, when done, the video URL.

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_job_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesThe job id returned by create_video.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does meaningful work: it enumerates the possible status values (queued, rendering, upscaling, done, failed) and states the conditional return of a video URL when done. It does not cover behavior on an unknown/invalid job id or whether repeated polling is expected, which keeps it below a 5.

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?

Two tight sentences, front-loaded with the action and followed by the return contract; nothing is wasted. Slightly denser than ideal only because the return details are crammed into one clause.

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 one-parameter read tool with no output schema, the description appropriately explains what comes back, including the status vocabulary and the conditional URL. Missing only edge-case behavior for invalid job ids and polling cadence, which are minor for this complexity.

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?

The single parameter is already fully documented in the schema, which even notes it is 'returned by create_video.' The description's phrase 'by its job id' adds no syntax, format, or constraint information beyond that, so the baseline 3 applies.

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 the status of an Epic Video generation job') and identifies the lookup key ('by its job id'), which clearly separates it from create_video, list_my_videos, and list_characters. It stops short of explicitly distinguishing itself from list_my_videos, which could plausibly surface status too.

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

Usage Guidelines3/5

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

Usage is only implied: the agent must infer that this is the polling call to make after create_video submits a job. There is no explicit when-to-use, when-not-to-use, timing/polling guidance, or named alternative.

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.