Skip to content

Worklittle Jobs status

Answered our latest tool-list check 21 hours ago with 22 tools. It will be marked verified after 3 successful checks in 7 days.

Answered (30 days)
1 of 1 checks
Last seen working
16 Nov, 18:17 UTC
Last commit
—
Licence
Not stated

Live checks

We call this hosted server's tools/list endpoint without credentials, from the public internet, every day while it answers and weekly otherwise.

  • Answered
  • Needs sign-in
  • No answer
Checked (UTC)ResultResponse timeTools
16 Nov, 18:17Answered0.3 s22

Tools (22)

Read from the server on 16 Nov 2026.

search_jobs
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_k
search_companies
Jobs — 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 —
get_job_details
Jobs — 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.
create_resume
Jobs — Write a one-page resume for the user from what they tell you (work history, skills, education) or their saved profile, fitted to a job when job_id is given. Never invent facts. When details are thin, pass draft true and fill the [ ] gaps with them. When it is their new or updated main resume, pass save_to_profile true to save it to their profile in the same call (ask first; it replaces the
get_market_overview
Jobs — 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.
add_applied_job
Jobs — 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.
get_my_profile
Jobs — 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.
create_sign_in_link
Jobs — Create a one-time link that opens worklittle.com signed in as the user (used by the app's buttons).
logout_connected_account
Jobs — Sign the user out of Worklittle in this app.
upload_my_resume
Jobs — 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
Jobs — 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
Jobs — Delete the user's main resume from their profile. Other saved resumes stay.
update_my_profile
Jobs — 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.
apply_for_job
Jobs — 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_s
check_application_status
Jobs — 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
Jobs — 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
Jobs — 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
Jobs — 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 app
save_about_me
Jobs — 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_pro
list_applications
Jobs — 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_i
get_apply_settings
Jobs — 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
Jobs — 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.