Check an application run
getApplicationRunSee how an applyToJob run went. state is running, finished or crashed. When finished, outcome is submitted (sent and confirmed by the employer's site; it is on their tracker as applied), submit_unconfirmed (submit clicked but no confirmation; do not resend), ready_to_submit (a dry run, every field filled, nothing sent), needs_input (nothing sent; ask the candidate each question in needsInput, then call applyToJob again with answers), blocked (a CAPTCHA or login wall, see blockers) or failed (nothing was sent, see blockers for why). A profile_gap question is worth saving to the candidate's profile with editPreferences too. editable lists the answers Clera filled in for them (question, answer, options); when the candidate wants one changed, call applyToJob again with answers { : }. verificationCodeRequested means the employer emailed a code: if the run applied with the Clera apply address it usually reaches the form on its own, so check again and look in readApplyInbox before asking the candidate for it.
Clera privately records this tool's inputs and results for usage tracking and support.
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": {
"runId": "<runId>"
},
"name": "getApplicationRun"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| runId | Yes | The runId applyToJob returned. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| error | Yes | ||
| state | Yes | ||
| fields | Yes | ||
| outcome | Yes | ||
| blockers | Yes | ||
| editable | Yes | ||
| needsInput | Yes | ||
| resumeAttached | Yes | ||
| verificationCodeRequested | Yes |