get_check_job
Read progress and usage reservation for an asynchronous source-link check job.
Hosted MCP registration verified. These schemas describe the development contract; confirm supported inputs with tools/list. Generic CLI/HTTP calls require a matching development server. Configure LINKTRAIL_API_URL; production does not expose these command routes.
Reading saved data does not start a verification job. Mutations can change saved records or access; the effects below apply.
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 instructuredContent 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
A succeeded job can carry an unknown observation. Read the watch history to inspect evidence separately from execution state.Output fields
Fields inside optional or nullable parents apply only when that parent exists. Common schema conventions explain evidence states, empty lists and extensions.
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. Operation-specific errors includeUNAUTHORIZED, INSUFFICIENT_SCOPE, WORKSPACE_ACCESS_DENIED, INVALID_GRANT, JOB_NOT_FOUND.
See error recovery for status, scope, cooldown, cursor and retry handling. Unknown observations are result data and do not establish loss.