ASYNC
get_job_status
Poll a long-running MCP job by id. Returns the current status plus result or error once the worker finishes.
Poll a long-running MCP job by id. Returns the current status plus result or error once the worker finishes.
Status values: queued → running → completed | failed.
Pair it with any tool that hands back a job_id. Today only bulk_generate_access_codes enqueues one.
Annotations
Read-only
It reads and never changes anything.
Arguments
job_id*stringUUID of the async job to poll.
What it returns
{ "data": { "job_id": "0a4e7b96-c358-4d12-9f6b-25a8013ce74f", "tool_name": "bulk_generate_access_codes", "status": "completed", "result": { "count": 50, "batch_unique_key": "..." }, "error": null, "started_at": "2026-05-18T10:05:00Z", "completed_at": "2026-05-18T10:05:04Z" }}result and error are both null until the worker finishes; exactly one is populated afterwards. started_at is null while the job is still queued.
How it fails
AUTHENTICATION_REQUIREDno authenticated user on the request.
RESOURCE_NOT_FOUNDunknown job_id, or the job was started by a different user.
How is this guide?
Last updated on