Coding agent documentation index Fetch the complete documentation index at: https://docs.worklittle.com/docs-agent-manifest.json Use this file to discover all available pages before exploring further.

Jobs MCP — Tools (26 tools)

Tools (26 tools)

| Area | Tools |
| --- | --- |
| Search | `search_jobs`, `get_job_details`, `get_job_keywords`, `get_market_overview`, `search_companies` |
| Apply | `apply_for_job` (one job, up to 10 with `job_ids`, or `test: true` for a free practice run), `check_application_status`, `steer_application`, `submit_application`, `stop_application` |
| Applications | `list_applications`, `update_applied_job` |
| Settings | `get_apply_settings`, `update_apply_settings` |
| Profile and resumes | `get_my_profile`, `update_my_profile`, `save_about_me`, `upload_my_resume`, `get_my_resume`, `delete_my_resume` |
| Documents | `create_resume`, `create_cover_letter` (`draft: true` for a draft) |

Tools cost the same as the REST routes they call. apply_for_job and the document tools are paid; the rest are free. See Pricing. ATS and webhook tools are under Business MCP.

Tool catalog

The other 76 tools (posting, candidates, employees, email, HR documents, attendance, webhooks) are in Business MCP: /business/mcp/tools

- search_jobs: Shows Worklittle job cards for a place and an optional role. The cards scroll endlessly: jobs near the place first, then farther away. Send the place and the role as SEPARATE fields. Never write 'product manager in San Francisco' as one query. PLACE: always pass near_lat + near_lng (the city's coordinates, which you know) and location as the display name (e.g. 'San Francisco, CA'). radius_km 25-50 for a city. If the user names no place, omit all place fields; the cards…

- get_job_details: Fetch detailed information about a specific job, including full responsibilities, qualifications, and company details. Pass job_id from search_jobs when you have one. If the user asks for full details of a role without an id (e.g. the first software engineer job in Austin), pass query and optional location instead — the tool loads the first matching live listing.

- get_job_keywords: Get skill and technology keywords from live Worklittle job data. Pass job_id for one posting. If the user asks what keywords show up for a role (resume tailoring, 'data scientist jobs', applications) and you do not have a job_id, pass query instead (optional location). Returns keywords plus keyword_count. Do not require a prior search when the question is about a role in general.

- get_market_overview: Returns aggregate job-market statistics from Worklittle. Call with no args for the whole market (workplace and job-type mix, top hiring companies). When the user names a role and/or city (e.g. product managers in San Francisco), pass query and location. The filtered slice includes match count, top companies in the sample, and salary signals from listings that publish pay.

- create_resume: Create a hiring-manager-ready one-page resume (no placeholders). Uses only real facts from optional resume/profile/job context; omits unknowns. Optional formats: html, pdf (one-page pdf-lib), docx. Omit formats for default html+pdf. Alias format=html|pdf|docx. $0.01 per resume, charged only when returned.

- create_cover_letter: Create a hiring-manager-ready one-page cover letter (no placeholders). Same formats/format options as create_resume (default html+pdf). $0.01 per cover letter, charged only when returned.

- apply_for_job: 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. For a Worklittle-hosted posting also include name, email and resume. 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.

- check_application_status: Check an application Worklittle is filling out: its status, which form fields are filled, and a live view link. Only the status completed means it was submitted.

- submit_application: Send an application that stopped for review (apply_for_job with auto_submit false, status awaiting_submit). Call it only after the user has seen the answers from check_application_status and said to send it.

- stop_application: Stop an application that Worklittle is filling out for the user. This cancels the application in progress and it cannot be resumed; the user would have to start it again. Needs the session_id from apply_for_job or list_applications.

- steer_application: Change what an application in progress fills in, without stopping it. Use when the user says something about an application Worklittle is filling right now ("say my notice period is one month", "my friend Ana Ruiz referred me", "I need visa sponsorship for the US", "make that answer shorter"). Pass their wish as plain instructions with their exact facts; never add facts. Works while the application is running, ready to submit, or waiting for answers. Needs the session_id…

- list_applications: List the user's applications, newest first: ones Worklittle is filling out now (status active, with session_id to check or stop), pending ones (matched by auto-apply or waiting for approval) and finished ones (completed = submitted, failed, stopped). Use days for a period (7 = the last week). Check it before applying so the same job is never applied to twice. Filter with status, days, job_id or applicant_id.

- get_apply_settings: Get the user's apply settings: auto_apply (Worklittle applies to matching jobs on its own), auto_submit (submit without a review stop) and tailor_resume (tailor the resume to each job).

- update_apply_settings: Change how Worklittle applies for the user. Use when they ask Worklittle to apply to matching jobs on its own, to send applications without stopping for their review, or to tailor their resume to each job (or to stop any of these). Only send the settings to change.

- list_applied_jobs: List the user's applied jobs (Saved, In progress, Applied, Interview, Offer, Rejected, Withdrawn), the same list as Applied and Saved on worklittle.com. Applying on worklittle.com or through Worklittle adds jobs here automatically.

- add_applied_job: Add a job to the user's applied jobs (Applied and Saved on worklittle.com) at a status such as saved or applied. To move a job already there, use update_applied_job.

- update_applied_job: Move a tracked job to a personal pipeline stage: saved, in_progress, applied, interview, offer, rejected, or withdrawn. Use after your agent learns the candidate progressed (or was rejected/withdrawn).

- delete_applied_job: Remove a job from the API key owner's personal saved-jobs pipeline (unheart / remove from Saved).

- get_my_profile: Get the user's Worklittle profile (name, location, contact details and job preferences). If they have not linked their account it returns connected false; use get_my_resume or apply_for_job to sign them in.

- upload_my_resume: Save the resume the user attached in the chat (PDF, Word, text or image) as the main resume on their Worklittle profile so it can be used to apply. It replaces the current main resume; other saved resumes (an account keeps up to 5) stay. Pass the attached file as resume_file.

- get_my_resume: Get the user's main resume: its status (ready, processing or missing) and, when ready, the resume text and profile details read from it. Use it to tailor advice or an application to the user's real experience.

- delete_my_resume: Delete the user's main resume from their profile. Other saved resumes stay.

- update_my_profile: Update the user's Worklittle profile, such as name, location, phone, links or the kind of job they want. Only send the fields to change.

- save_about_me: Save standing facts about the user that Worklittle uses on every future application it fills: work authorization and visa sponsorship by country, relocation, notice period, desired salary, languages, qualifications, who referred them, or other standing answers they ask applications to use. Stored as the 'More about you' text in their Settings. Pass the complete text to keep (read get_my_profile first and merge with what is there, so nothing is lost). Write it in the…

- search_companies: Search the Worklittle market company index by name or slug (ranked typeahead). Returns id, name, slug, logo_url, and enrichment fields for employers with open jobs. Use when the user names an employer and you need a real slug/id for search_jobs company= filters, job alerts, or automations. If zero hits, try alternate spellings or related employer names from further search_companies calls — do not invent company ids or slugs. If still empty, tell the user that employer is…

- create_sign_in_link: Create a one-time link that opens worklittle.com signed in as the user (used by the app's buttons).