Update job status
update_job_statusUpdate a saved job's status, outcome or details. Use status for where the application is now (interviewing, negotiation for an offer, hired). Use outcome for an applied job that ended without progressing: rejected, no_response (no reply after 45+ days), withdrawn, or didnt_apply; status stays as it is. With didnt_apply, give a reason: job_closed reports the listing as expired, and the rest improve the user's future matches. Add detail for anything worth knowing (what the page said, a hidden requirement). Uses the connected Himalayas account; no extra sign-in needed.
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": {
"id": "<id>"
},
"name": "update_job_status"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Kanban item ID | |
| notes | No | Updated notes | |
| detail | No | Anything worth knowing about the outcome, in a sentence or two. No personal data. | |
| reason | No | Why the user didn't apply (only with outcome didnt_apply) | |
| status | No | New application status | |
| outcome | No | What happened after applying, as reported by the user. "clear" removes a recorded outcome. | |
| excitement | No | Excitement level from 0-5 |