Skip to main content
Glama

Get Job Status

get_job_status
Read-onlyIdempotent

Check the status and result of an asynchronous BGRemover Video background-removal job using its job_id, including output_url once processing completes.

Instructions

This tool will fetch the status and result of an asynchronous BGRemover Video job (returned by remove_video_background). Status is one of queued, processing, completed, failed; when completed the response includes output_url. It takes the following argument: - job_id (str, required): The job_id returned by the asynchronous tool call.

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 remove_video_background.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (read-only, idempotent, non-destructive), and the description adds real value beyond them by enumerating the state machine (queued, processing, completed, failed) and noting output_url appears on completion. It omits polling cadence, retention/expiry of job records, and what a failed response contains.

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?

Front-loaded with the purpose and status semantics in one dense sentence; the trailing '- job_id (str, required)' bullet largely repeats the schema and could be dropped. Overall tight with minimal waste.

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 no output schema, the description carries the return-value burden and does reasonable work by naming the possible statuses and the output_url on success. For a single-parameter read tool this is nearly sufficient, though failure payloads and polling behavior remain unspecified.

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 coverage is 100% and the single parameter is fully documented in the schema, so the schema already does the heavy lifting. The description only restates that job_id is required and comes from remove_video_background, adding provenance but no format or validation detail beyond the schema.

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?

States a specific verb and resource (fetch status/result of an asynchronous BGRemover Video job) and ties it directly to the sibling that creates the job, remove_video_background. An agent can distinguish it from siblings without opening any schema.

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?

Usage is clearly implied: call this after remove_video_background for the job_id it returned. It doesn't state exclusions or polling guidance (e.g., how often to poll, when to stop), which keeps it out of 5 territory.

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