Botverse

Get Job Status

get_job_status

Read-onlyIdempotent

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.

Input Schema

TableJSON 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

TableJSON Schema

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

TDQS

A4.5/5.0

Behavior5/5

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

The description discloses key behavioral traits: intermediate statuses like 'queued' or 'processing' are normal, large files take 5–15 minutes, and polling must continue indefinitely without a fixed attempt limit. This adds significant value beyond the readOnlyHint and idempotentHint annotations, which only indicate safety. It also warns against stopping early, preventing agent misuse.

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 front-loaded with purpose and then provides actionable polling rules. Every sentence serves a distinct purpose: status scope, polling interval, expected durations, and a caution against premature stopping. No redundant filler exists.

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?

The tool is simple with one parameter and a full output schema. The description covers all necessary operational context: how often to poll, what statuses to expect, and how long to continue. Combined with annotations, there is no missing information for an agent to correctly invoke the tool.

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 input schema already fully documents job_id with descriptions listing the exact source tools. The description does not add additional parameter semantics, so it relies on the schema's comprehensive coverage. This meets the baseline for schema coverage.

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 states 'Poll the status of a transcode or convert job,' clearly identifying the action and resource. It distinguishes from sibling tools like get_workflow_status by specifying the job type, and also provides explicit polling behavior. This is a specific, non-tautological statement.

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?

The description gives explicit polling instructions: 'Call every 5 seconds until status is complete or failed' and 'Keep polling indefinitely until a terminal status is reached.' It defines the scope as transcode/convert jobs, but does not explicitly contrast with alternative tools like get_workflow_status. Therefore, it provides clear context and usage guidance, but misses explicit alternatives.

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

All Botverse tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0

Disambiguation4/5

Tools are largely distinguishable by their action and input source (content/file/url), but the multiple convert_* and transcode/transcribe variants overlap in purpose, and get_job_status vs get_workflow_status could cause confusion. Descriptions are thorough enough to guide selection, but the boundaries between similar actions are not always crisp.

Naming Consistency4/5

All names use snake_case with a verb-noun pattern (get_, convert_, transcode_, transcribe_, submit_, cancel_), which is consistent. However, the variant naming is not perfectly parallel: convert_content/file/from_url use a source suffix, whereas transcode_video vs transcode_from_url and transcribe_media vs transcribe_from_url mix output type and source, creating minor inconsistency.

Tool Count4/5

At 15 tools, the server is at the upper end of a well-scoped set. Each tool supports a distinct input/output route or workflow function, but the count is slightly heavy due to multiple variants of similar operations. It remains appropriate for the breadth of conversion, transcoding, transcription, workflow, and wallet features.

Completeness3/5

The core job lifecycle (submit, poll, retrieve output) is well covered, and workflows have submit/status/cancel. However, get_upload_url references a transcode_content tool that does not exist in the toolset, and there is no way to cancel a single job (only full workflows). This leaves gaps for inline media transcoding in sandboxed environments and granular job control.

Resources

Need Help?