Botverse

get_job_status

Read-onlyIdempotent

Poll the status of a transcode or convert job every 5 seconds until completion or failure. Continue polling indefinitely until a terminal status is reached.

Instructions

Poll the status of a transcode or convert job. Call every 5 seconds until status is 'complete' or 'failed'. Status 'queued' or 'processing' is normal — large files take 5–15 minutes. Keep polling indefinitely until a terminal status is reached. Do not stop polling after a fixed number of attempts.

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

Name	Required	Description	Default
`job_id`	Yes	Job ID returned by transcode_video, transcode_from_url, convert_file, convert_from_url, or convert_content.

Output Schema

Name	Required	Description
`job_id`	Yes	The job identifier.
`status`	Yes	Current job state.
`progress_pct`	No	Encoding progress 0–100. Only present while status is 'processing'.
`output_key`	No	storage object key of the completed output. Present when status is 'complete'. Pass to get_download_url.
`cost_usd`	No	Amount debited from the wallet on completion, in USD.
`error_message`	No	Human-readable error description. Present when status is 'failed'.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.4Jun 17, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds essential polling specifics (5s interval, indefinite loop, expected durations), far exceeding the annotations' baseline.

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 concise sentences, all necessary, no redundancy. The most critical information (purpose and polling behavior) is front-loaded, with no wasted words.

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?

For a simple polling tool with a single parameter, an existing output schema, and rich annotations, the description fully covers the how (polling mechanics), when (until terminal), and what to expect (status values and timing).

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 description coverage is 100% for job_id, with a clear description of its source (returned by job-creating tools). The description adds no new parameter semantics beyond reinforcing that job_id comes from those tools.

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?

The description starts with a specific verb 'Poll' and resource 'status of a transcode or convert job', clearly distinguishing it from sibling tools that create or manage jobs (e.g., transcode_video, cancel_workflow).

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

Usage Guidelines5/5

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

Provides explicit polling instructions: interval (5 seconds), terminal states ('complete' or 'failed'), non-terminal states explanation ('queued'/'processing' normal, 5-15 minutes), and a strong directive to poll indefinitely, not stop early.

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

Deploy Server