Worklittle Jobs
Server Details
Find jobs near you and apply instantly. Search over 7.5 million listings by role, pay and visa.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2024-11-05
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 22 tools
Most tools have clearly distinct purposes and the descriptions actively cross-reference each other (add_applied_job vs update_applied_job/apply_for_job, steer vs submit vs stop_application). The main soft spot is add_applied_job vs apply_for_job, and save_about_me vs update_my_profile, which both touch stored user facts; the descriptions disambiguate but the boundaries require careful reading.
Every tool is snake_case with a verb_noun shape (search_jobs, apply_for_job, check_application_status, update_apply_settings, upload_my_resume). Paired resources use symmetric naming (get/update_apply_settings, get/update_my_profile), so the pattern is highly predictable.
22 tools is at the upper edge but each maps to a real operation across search, apply lifecycle, resume, profile, settings and auth. A couple could plausibly merge (get/update settings, profile read/update), but nothing feels redundant or padding.
Core flows are fully covered: search, detail lookup, apply with review/steer/stop/submit, application listing, resume create/read/upload/delete, profile and settings read/update, and auth. Gaps are minor: no job-alert or automation management (referenced in search_companies), no way to list the other saved resumes or remove an entry from the applied/saved list.
Available Tools
22 toolsadd_applied_jobJobs · Add Applied JobADestructiveIdempotentInspect
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.
Inputs: job_id (required), job_title (required), company_name (required), method, +2 more. Returns: JSON result from this Worklittle MCP tool.
apply_for_jobJobs · Apply For JobADestructiveInspect
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. 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.
Inputs: url, test, urls, job_id, +12 more. Returns: JSON result from this Worklittle MCP tool.
check_application_statusJobs · Check Application StatusBRead-onlyIdempotentInspect
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.
Inputs: session_id (required). Returns: JSON result from this Worklittle MCP tool.
create_resumeJobs · Create ResumeADestructiveInspect
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 current main resume). Costs $0.01.
Inputs: draft, format, job_id, formats, +5 more. Returns: Mutation result from the Worklittle API (created or updated resource).
create_sign_in_linkJobs · Create Sign In LinkAInspect
Jobs — Create a one-time link that opens worklittle.com signed in as the user (used by the app's buttons).
Inputs: no named parameters. Returns: Mutation result from the Worklittle API (created or updated resource).
delete_my_resumeJobs · Delete My ResumeADestructiveIdempotentInspect
Jobs — Delete the user's main resume from their profile. Other saved resumes stay.
Inputs: no named parameters. Returns: Delete or stop confirmation from the Worklittle API.
get_apply_settingsJobs · Get Apply SettingsARead-onlyIdempotentInspect
Jobs — Get the user's apply settings: auto_apply (Worklittle applies to matching jobs on its own), auto_submit (submit without a review stop), tailor_resume (tailor the resume to each job) and max_per_company (most applications to one company in any 30 days; say it with the 30 days).
Inputs: no named parameters. Returns: Read result from the Worklittle API.
get_job_detailsJobs · Get Job DetailsARead-onlyIdempotentInspect
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.
Inputs: query, job_id, location. Returns: Detailed Worklittle job record.
get_market_overviewJobs · Get Market OverviewARead-onlyIdempotentInspect
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.
Inputs: query, location, workplace_type. Returns: Aggregate job market stats for the requested filters.
get_my_profileJobs · Get My ProfileARead-onlyIdempotentInspect
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.
Inputs: no named parameters. Returns: Read result from the Worklittle API.
get_my_resumeJobs · Get My ResumeARead-onlyIdempotentInspect
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.
Inputs: no named parameters. Returns: Read result from the Worklittle API.
list_applicationsJobs · List ApplicationsARead-onlyIdempotentInspect
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_id or applicant_id. total counts every match; when next_offset is set, call again with that offset for the rest.
Inputs: days, limit, job_id, offset, +2 more. Returns: Read result from the Worklittle API.
logout_connected_accountJobs · Logout Connected AccountBDestructiveIdempotentInspect
Jobs — Sign the user out of Worklittle in this app.
Inputs: no named parameters. Returns: JSON result from this Worklittle MCP tool.
save_about_meJobs · Save About MeADestructiveIdempotentInspect
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_profile first and merge with what is there, so nothing is lost). Write it in the user's words; never invent facts.
Inputs: about_me (required). Returns: JSON result from this Worklittle MCP tool.
search_companiesJobs · Search CompaniesARead-onlyIdempotentInspect
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 — do not invent company ids or slugs. If still empty, tell the user that employer is not in the index yet and offer any close matches you found.
Inputs: q (required), limit. Returns: Read result from the Worklittle API.
search_jobsWorklittle JobsARead-onlyIdempotentInspect
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 start at the user's approximate (IP-based) area. When a search runs short, results continue with close matches (search.scope related: same role and place with seniority, salary, job type and date filters dropped), then the rest of the country and worldwide (search.scope country or world), so say which cards are exact matches and where the roles are. ROLE: query holds only the job title text (e.g. 'product manager') and may be omitted for 'any job'. Search Worklittle job listings. People say Worklittle plus a role, city, company, or filters (or just 'jobs') — they will not name this tool. Call it whenever they want Worklittle jobs. Search by keyword, company, location, job type, seniority, or recency. Use for ANY industry (retail, finance, healthcare, tech, etc.). Search matches title and filter text (substring / FTS), not vector embeddings. Role / title text goes in query (+ optional keywords). The API matches job TITLE substrings only for that text — it does not mix company names into the same field. Preserve negative title terms with a leading dash, e.g. 'software engineer, -senior' excludes titles containing senior. Use company for employer slugs (include or exclude). Never concatenate many job titles into one query unless the user supplied comma-separated roles. Do not add seniority_level, stacks, or resume-derived terms unless they asked. Omit seniority_level unless they explicitly name a level as an inclusion filter (never infer from profile). Expand abbreviations only; umbrella phrases use neutral roles and/or company slugs. Umbrella or vague phrases ('big tech', 'FAANG', 'top retailers'): interpret intent, then one search_jobs with comma-separated company slugs and/or a broad role query — prefer one API call over many. company MUST be employer slug(s): bare slugs include (OR), e.g. meta,google,apple. Prefix a slug with '-' to exclude, e.g. -lucid-motors,-tesla. Same leading-dash rule as title negatives, but in company not query. Expand 'no car companies' / 'don't show Lucid' into -slug tokens. Never pass display names as query. If unsure of slug, try lowercase hyphenated brand. Add skills or stack to query/keywords only when the user mentioned them — not from profile by default. When an include company filter returns 0 results, try a broader query (drop include company, use role keywords) before telling the user nothing matched. Pass cursor from a previous response to paginate. Search is anonymous. Do not call get_account, apply, or ask the user to Connect to search or skip. Connect / OAuth is only when they apply. After it runs, recommend the 3-5 jobs that fit the person best (one line each: title, employer, place, pay if listed, why it fits), then offer to apply to any or all of them instantly. No counts, stats or trivia. The person already sees every job in the app: never describe the interface ('cards above', 'map', 'widget'). Applying is just 'apply' (never 'Apply with AI'); when they pick, call apply_for_job (job_ids for several). For visa / H-1B: set visa_sponsorship to 'yes' (plus optional query). Postings must be explicitly tagged. When visa_sponsorship is set and posted_within_days is omitted, the last 30 days are searched instead of the default 7 — tagged visa roles are sparse. For regional / nearby intent: near_lat, near_lng, radius_km (e.g. 50–65). Prefer this over the location substring when coordinates are known. For two or more metros in one user message (e.g. SF or NYC), pass location_or as comma-separated place names — one API request matches ANY listed place. Do not use near_* for multi-metro; use location_or or location with 'or' between cities. Recency: set posted_within_days from the user's words — today/just posted → 1; past few days → 3; this week → 7; past two weeks → 14; this month → 30. Omit when they did not mention timing (defaults to the last 7 days). Jobs older than 30 days are never returned; 0 means the full 30 days. Never put today/new/this week into query. Filters are only these: posted_within_days (Past 24 hours / 3 / 7 / 14 / 30 days), seniority_level (Experience: intern, entry/new grad, senior, manager, director/executive), employment_type (Type: full-time, part-time, contract), and visa_sponsorship (Visa). Prefer no filters: use one only when the user explicitly asks for it, because each filter shrinks the results a lot. For remote-only jobs send remote: true (and no place fields). There is no salary, hybrid, or benefits filter. If the user asks to filter by salary, search without it and say they can see salaries on the cards (listed pay shows on each card).
Inputs: limit, query, cursor, remote, +16 more. Returns: Paginated job search results from Worklittle.
steer_applicationJobs · Steer ApplicationADestructiveInspect
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 application is running, ready to submit, or waiting for answers. Needs the session_id from apply_for_job or list_active_applications. For facts that should apply to every future application too, also call save_about_me.
Inputs: session_id (required), instructions (required). Returns: JSON result from this Worklittle MCP tool.
stop_applicationJobs · Stop ApplicationADestructiveIdempotentInspect
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.
Inputs: session_id (required). Returns: JSON result from this Worklittle MCP tool.
submit_applicationJobs · Submit ApplicationADestructiveIdempotentInspect
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.
Inputs: session_id (required). Returns: JSON result from this Worklittle MCP tool.
update_apply_settingsJobs · Update Apply SettingsAIdempotentInspect
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.
Inputs: auto_apply, auto_submit, tailor_resume. Returns: Mutation result from the Worklittle API (created or updated resource).
update_my_profileJobs · Update My ProfileBDestructiveIdempotentInspect
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.
Inputs: phone, x_url, you_name, you_work, +28 more. Returns: Mutation result from the Worklittle API (created or updated resource).
upload_my_resumeJobs · Upload My ResumeADestructiveInspect
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.
Inputs: mime, filename, resume_file, content_base64. Returns: JSON result from this Worklittle MCP tool.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Search 3M+ live job postings: salaries, filters, similar roles and CV matching. Free, no account.
Search 1.2M+ open jobs from 22k companies, read full listings and look up employers.
Search 6.3M+ live jobs from companies' own career pages, plus resume tailoring & cover letters.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceAI Job search over 3.5M+ live US jobs2MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to evaluate job postings under a UK visa constraint, including sponsor-licence checks with confidence grades, screening for seniority and hard requirements, and role searches that exclude recruitment agencies. It also tracks application history to help avoid duplicate applications.4MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to search, filter, and apply to salary-transparent tech jobs across nine international job boards, including Switzerland's jobs.ch and jobup.ch and Singapore's MyCareersFuture. Results are returned as JSON with salary, remote, tech, and posting-date filters, and previously applied postings are remembered so they drop out of subsequent listings.-
- FlicenseNot gradedqualityAmaintenanceLets AI agents search, filter, and apply to salary-transparent tech jobs across nine job boards in eight countries, filtering by pay, remote work, tech stack, and location while tracking applications to avoid duplicates. It returns JSON-first results so an agent can drive job discovery and application end-to-end from the terminal or chat.-
Glama MCP Gateway
Add one secure layer between your agents and this server.