Skip job
skip_jobRecord that the user is passing on a Himalayas job, with the reason, so it stops coming back in get_new_matches and future matches can learn from it. job_closed also reports the listing as expired. For a job already in the tracker, use update_job_status with outcome didnt_apply instead. 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": {
"company_slug": "<company_slug>",
"job_slug": "<job_slug>",
"reason": "<reason>"
},
"name": "skip_job"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| detail | No | Anything worth knowing, in a sentence or two (what the page said, a hidden requirement). No personal data. | |
| reason | Yes | Why the user is passing on it | |
| job_slug | Yes | Job slug (from the job listing URL) | |
| company_slug | Yes | Company slug (from the job listing URL) |