Apply to a job from AIApply search
apply_to_jobUse this when the connected user wants AIApply to apply to a job they picked from search_jobs. AIApply adds it to their queue already approved, so it does not wait for anyone: it will be applied for and that spends a credit. This is the only point the user is asked, so call it without confirmed, show them the job, ask them, then call again with confirmed=true. Adding the same job twice is refused rather than repeated. If the account is not set up yet, it says so: call get_setup_status first. Needs an AIApply account: if the user has not signed in, calling it asks them to sign in or create one. It also needs a permission the user grants; if it was not granted, calling it asks the user to allow it. A job_id from search_jobs stays valid after either.
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": {
"search_job_id": "<search_job_id>"
},
"name": "apply_to_job"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| confirmed | No | True only after the user has explicitly agreed to apply for this job. | |
| search_job_id | Yes | The job_id from search_jobs. Not the job_id from list_review_jobs. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| error | No | True when the job could not be added. | |
| queued | No | True only when the job was added. | |
| reason | No | Why nothing was added, when nothing was. | |
| message | Yes | ||
| user_message | No | Show this to the user rather than message. | |
| applies_after | No | applying_active when the job waits in the queue until applying is active on the account. | |
| dashboard_url | No | The AIApply dashboard, where the user manages Auto Apply. | |
| updates_offer | No | Present once, when the account is first ready: something you may offer the user. Act on it only if they agree. |