Diagnose what happened to an extraction
datasheetvend_diagnose_extractionExplain what happened to an extraction, module by module, from recorded state. Keep the outcomes apart: never_requested (not asked for, not a failure), nothing_found (ran; the datasheet does not document it), needs_review, still_running and failed (a recorded error). When failureReason is present, lead with whose problem it is (our_infrastructure means re-running is worth it). Quote the recorded reason, never invent one; if unexplained is true, say nothing was recorded. Recorded error messages longer than 500 characters are cut (errorMessagesCut). Reads the recorded state of your account's own jobs (owner, or TEAM-shared in your workspace; a refunded job is refused): nothing is extracted and no model is called. Costs no credits. Needs a DatasheetVend API key.
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": "datasheetvend_diagnose_extraction"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| job_id | Yes | An extraction job in your account. |