Skip to main content
get_check_job Read progress and usage reservation for one asynchronous check job, placement (job_ ids) or destination (tjb_ ids).
Available in the deployed MCP and HTTP bundle. Confirm access and inputs with your connected catalog. Workspace scopes and enabled providers still apply.
This read does not start a verification job.

Example request

Connect through MCP, CLI, or HTTP. Replace example identifiers with records from your workspace.

Returned result

Illustrative data validated against the documented response schema. IDs and dates are examples, not a live account capture. MCP returns this data in structuredContent and in a text content block; generic HTTP and CLI return the JSON result directly.

Input fields

Omit optional fields when you do not want to supply them. Null is accepted only where listed. Unknown input properties are rejected.

Validation and omitted values

Job ids carry their kind: job_ ids are placement checks, tjb_ ids are destination checks. The retired name get_target_job resolves here. A succeeded job can carry an unknown observation. Read the watch history to inspect evidence separately from execution state. A succeeded job can carry an unknown observation. Read destination history for its evidence and reason.

Output fields

Fields inside optional or nullable parents apply only when that parent exists. Common schema conventions explain evidence states, empty lists and extensions.
  • id (string, required): Resource identifier returned by the operation.
  • state (string, required): Saved lifecycle or evidence state, as enumerated for this record. values: “queued”, “running”, “succeeded”, “failed”, “cancelled”
  • workspace_id (string, required): Workspace that owns this record.
  • project_id (string, required): Project that owns this record.
  • watch_id (string, optional): Identifier returned by the related operation.
  • target_id (string, optional): Identifier returned by the related operation.
  • type (string, optional).
  • execution_mode (string, optional).
  • idempotency_key (string, required): Caller retry identifier, bound to the original request arguments.
  • payload_hash (string, required).
  • attempt_count (number, required).
  • max_attempts (number, required).
  • lease_token (string / null, required).
  • lease_expires_at (string / null, required).
  • error_code (string / null, required): Latest delivery detail code; null when no failure or retry has been recorded.
  • error_message (string / null, optional).
  • created_at (string, required): UTC timestamp when the record was created.
  • updated_at (string, required): UTC timestamp of the last record update.
  • completed_at (string / null, required).
  • replayed (boolean, optional): True when the response reuses an earlier request with the same idempotency value.
  • usage (object / null, optional).
Download input schema · Download output schema

Errors and retries

The command is annotated idempotent. Reuse an accepted idempotency key when the input provides one; changing the payload under a reused key can conflict. See error recovery for status, scope, cooldown, cursor and retry handling. Unknown observations are result data and do not establish loss.

HTTP resource routes

These existing resource routes share the operation’s domain behavior. Their parameter placement, status and response envelope can differ from generic invocation. See HTTP route details.

Continue

get_history Follow the related workflow, inspect capability status, or return to the command index.