Apply
hunt_applyRecord an application actually submitted. One per posting. One application per posting (JH-4) — the duplicate guard exists so the SAME role through two agencies gets a decision, not two submissions. applied_at accepts the literal "unknown" when the submission is real but the date was never recorded — never guess a date (JH-1). Record the resume version that actually went out (JH-10). Effects: application created; posting -> applied; submission logged as a touch.
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": {
"posting_id": "<posting_id>"
},
"name": "hunt_apply"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| channel | No | ||
| applied_at | No | ISO date, or the literal "unknown" — never a guess (JH-1). | |
| posting_id | Yes | The posting. | |
| via_contact | No | Recruiter who submitted, e.g. HC-0001 — for the double-submission audit. | |
| resume_version | No | What was actually sent — label or id (JH-10). |