Jobs · Apply For Job
apply_for_jobJobs — Apply to jobs for the user: Worklittle fills out and submits each application. Pass job_id from search_jobs, or job_ids (up to 10) when they want to apply to several or all of them at once. Worklittle-hosted postings work the same way: their form is filled from the user's profile. It submits by default; pass auto_submit false when the user wants to review first, then show them the answers from check_application_status and send it with submit_application only after they say so. If it answers RESUME_REQUIRED or resume_warning, the user has no résumé saved: follow next_step (upload theirs with upload_my_resume, or write one with create_resume and save_to_profile true) and apply again.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "apply_for_job"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | Instead of job_id: a link to the job posting (the employer's job page or application page), when the user pastes one. Worklittle finds the job, or adds it if it isn't listed, and applies; the result includes its job_id. If it can't apply through the link, the error says why and lists similar_jobs. | |
| test | No | true: a free practice run. Nothing opens, nothing is stored or sent to an employer, no personal information needed. The session moves queued → running → completed over ~25 seconds. | |
| urls | No | Like job_ids, for job posting links (can be combined with job_ids, up to 10 jobs in all). Each result includes its url and job_id. | |
| job_id | No | Worklittle job id from search_jobs / get_job_details. | |
| job_ids | No | Apply to up to 10 jobs in one call (instead of job_id), all for the same person and with the same options. Returns one result per job. | |
| applicant | No | With use_profile false: the person applying. name and email are required; phone, city, state, country, work_authorization, needs_sponsorship, desired_salary, about_you are recommended. Send their resume as resume_text or resume_pdf_base64. | |
| resume_id | No | Use this one of the user's saved resumes. Leave out to let Worklittle pick the best one for the job. | |
| auto_submit | No | Default: the user's auto_submit setting (on unless they turned it off), which submits when the form is complete. false: stop at review (status awaiting_submit) so the user can check every answer; send it with submit_application. | |
| resume_html | No | Optional resume HTML to seed. | |
| resume_text | No | With use_profile false: the applicant's resume as plain text. | |
| use_profile | No | Default true: apply as the signed-in user with their profile. false: apply as the applicant described below (another person, no Worklittle account needed). | |
| applicant_id | No | With use_profile false: the person from an earlier apply. Store it permanently with the person and reuse it; it works with any Worklittle API key. It is also emailed to them; if lost, ask them for it. | |
| tailor_resume | No | Default from apply settings (on): write a resume tailored to this job. false: send the resume as is. | |
| max_per_company | No | Applications to one company per 30 days for this person. Defaults to their apply setting (3). Raise it only after the person agrees, when a start returned COMPANY_LIMIT_REACHED. | |
| cover_letter_html | No | Optional cover letter HTML to seed. | |
| resume_pdf_base64 | No | With use_profile false: the applicant's resume PDF, base64. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||