Skip to main content
Glama

Worklittle Jobs

Worklittle Jobs

search_jobs
Read-onlyIdempotent

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).

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": "search_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of results to return, at most 8 per call. Pass cursor from the response for more.
queryNoJob title or role phrase (merged with keywords). Sent as API title= — matches job TITLE text only, separate from company. Preserve negative title terms with a leading dash, e.g. 'product manager, software engineer, -senior'. If they want any role / all jobs, omit. Never merge many titles into one string unless the user supplied comma-separated roles. Expand shorthand (swe, pm, sre) when applicable.
cursorNoPagination cursor from a previous search_jobs response to fetch the next page.
remoteNotrue: remote jobs only (any country unless country is set). Leave out place fields. location 'remote' does the same.
appliedNoFilter by whether the user already applied. false: leave out jobs they applied to. true: only jobs they applied to. Omit to get every job; ones they applied to say applied: true.
companyNoEmployer slug(s): bare slug or comma-separated OR include (e.g. meta,google,apple). Prefix with '-' to exclude (e.g. -lucid-motors,-tesla). Mix allowed (meta,google,-amazon). Lowercase hyphenated. Mid-slug hyphens are part of the slug; only a leading '-' excludes. If include-only returns 0, retry without include slugs.
countryNoISO 3166-1 alpha-2 country filter (e.g. US, GB, DE). Returns jobs in that country or workplace_type remote.
keywordsNoOnly if the user named skills or stacks in this turn. Omit by default — do not pull from resume or profile.
locationNoDisplay name of the place (e.g. 'San Francisco, CA'). When near_lat/near_lng are set this is only a label and is NOT used as a text filter. Otherwise a text filter on job location strings (partial match). For metro-area or 'near me' intent, prefer near_lat + near_lng + radius_km (50–65 km typical) so results are not tied to one city spelling. Use location only when you cannot geocode, or as a fallback. Avoid long 'City, Country' strings; use country for country filters. For multiple metros, prefer location_or.
near_latNoLatitude for distance search. Use with near_lng. Typical source: browser geolocation or geocoded city.
near_lngNoLongitude for distance search. Required with near_lat.
radius_kmNoRadius in kilometers around near_lat/near_lng. Default 50, max 500.
exclude_idsNoComma-separated job IDs to exclude (e.g. postings already shown in the conversation).
location_orNoComma-separated place substrings when the user names two or more metros at once (e.g. San Francisco,New York). The API returns jobs whose location text matches ANY term. Mutually exclusive with distance search (near_lat/near_lng).
exclude_remoteNoDistance searches (near_lat/near_lng) return on-site and hybrid jobs in the radius. For remote jobs, search without near_lat/near_lng and set remote: true.
employment_typeNoType of employment contract.
seniority_levelNoOmit unless the user explicitly asked for a band. Never infer from profile. Enum when set:
visa_sponsorshipNoFilter by explicit visa sponsorship text in the posting (AI-extracted). Use 'yes' for jobs that sponsor visas (H-1B, etc.). Use 'no' only when the user wants roles that explicitly state no sponsorship. Omit when not relevant.
posted_within_daysNoDays of posted-date lookback, at most 30. Omit → default 7. 0 → the full 30 days. 1 → today/last 24h. 7 → this week. Jobs older than 30 days are never returned. Never encode recency words in query.
description_languageNoISO 639-1 code for the language of the job posting body. Examples: en, es, de, fr, pt.

Output Schema

NameRequiredDescriptionDefault
jobsNoMatching job listings.
queryNo
totalNoTotal matches when provided by the API.
cursorNoPagination cursor for the next page.
searchNoEcho of search_jobs filters for the Job Cards widget.
locationNo
near_latNo
near_lngNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / applied
      Added value: +{
      +  "description": "Filter by whether the user already applied. false: leave out jobs they applied to. true: only jobs they applied to. Omit to get every job; ones they applied to say applied: true.",
      +  "type": "boolean"
      +}
  2. Changed3 schema fields changed
    • changedInput schema / properties / exclude_remote / description
      Previous value: -"Distance searches (near_lat/near_lng) return on-site and hybrid jobs in the radius. For remote jobs, search without near_lat/near_lng and set workplace_type to remote."New value: +"Distance searches (near_lat/near_lng) return on-site and hybrid jobs in the radius. For remote jobs, search without near_lat/near_lng and set remote: true."
    • changedInput schema / properties / limit / description
      Previous value: -"Number of results to return. Default 10, max 50."New value: +"Number of results to return, at most 8 per call. Pass cursor from the response for more."
    • changedInput schema / properties / limit / maximum
      Previous value: -50New value: +8
  3. Changed1 schema field changed
    • changedInput schema / properties / exclude_remote / description
      Previous value: -"When using near_lat/near_lng: false includes remote-only jobs; true (default) excludes them so results are geographically local."New value: +"Distance searches (near_lat/near_lng) return on-site and hybrid jobs in the radius. For remote jobs, search without near_lat/near_lng and set workplace_type to remote."
  4. Changed1 schema field changed
    • changedInput schema / properties / posted_within_days / description
      Previous value: -"Days of posted-date lookback. Omit → default 7. 0 → no cutoff (any age). 1 → today/last 24h. 7 → this week. Any positive integer allowed (e.g. 90, 365). Never encode recency words in query."New value: +"Days of posted-date lookback, at most 30. Omit → default 7. 0 → the full 30 days. 1 → today/last 24h. 7 → this week. Jobs older than 30 days are never returned. Never encode recency words in query."
  5. Changed1 schema field changed
    • changedInput schema / properties / posted_within_days / description
      Previous value: -"Days of posted-date lookback. Omit → default 7 (map default). 0 → no cutoff (any age). 1 → today/last 24h. 7 → this week. Any positive integer allowed (e.g. 90, 365). Never encode recency words in query."New value: +"Days of posted-date lookback. Omit → default 7. 0 → no cutoff (any age). 1 → today/last 24h. 7 → this week. Any positive integer allowed (e.g. 90, 365). Never encode recency words in query."
  6. Changed1 schema field changed
    • addedInput schema / properties / remote
      Added value: +{
      +  "description": "true: remote jobs only (any country unless country is set). Leave out place fields. location 'remote' does the same.",
      +  "type": "boolean"
      +}
  7. Changed3 schema fields changed
    • changedInput schema / properties / posted_within_days / description
      Previous value: -"Days of posted-date lookback. Omit → default 14. 0 → no cutoff (any age). 1 → today/last 24h. 7 → this week. Any positive integer allowed (e.g. 90, 365). Never encode recency words in query."New value: +"Days of posted-date lookback. Omit → default 7 (map default). 0 → no cutoff (any age). 1 → today/last 24h. 7 → this week. Any positive integer allowed (e.g. 90, 365). Never encode recency words in query."
    • removedInput schema / properties / salary_min
      Removed value: -{
      -  "description": "Minimum annual salary in the job's listed currency. Only returns jobs where a salary is known and meets this threshold. Examples: 100000, 150000.",
      -  "minimum": 0,
      -  "type": "number"
      -}
    • removedInput schema / properties / workplace_type
      Removed value: -{
      -  "description": "Work arrangement.",
      -  "enum": [
      -    "remote",
      -    "hybrid",
      -    "on_site"
      -  ],
      -  "type": "string"
      -}
  8. Changed1 schema field changed
    • changedInput schema / properties / location / description
      Previous value: -"Text filter on job location strings (partial match). For metro-area or 'near me' intent, prefer near_lat + near_lng + radius_km (50–65 km typical) so results are not tied to one city spelling. Use location only when you cannot geocode, or as a fallback. Avoid long 'City, Country' strings; use country for country filters. For multiple metros, prefer location_or."New value: +"Display name of the place (e.g. 'San Francisco, CA'). When near_lat/near_lng are set this is only a label and is NOT used as a text filter. Otherwise a text filter on job location strings (partial match). For metro-area or 'near me' intent, prefer near_lat + near_lng + radius_km (50–65 km typical) so results are not tied to one city spelling. Use location only when you cannot geocode, or as a fallback. Avoid long 'City, Country' strings; use country for country filters. For multiple metros, prefer location_or."
  9. Changed1 schema field changed
    • changedInput schema / properties / location / description
      Previous value: -"Display name of the place (e.g. 'San Francisco, CA'). When near_lat/near_lng are set this is only a label and is NOT used as a text filter. Otherwise a text filter on job location strings (partial match). For metro-area or 'near me' intent, prefer near_lat + near_lng + radius_km (50–65 km typical) so results are not tied to one city spelling. Use location only when you cannot geocode, or as a fallback. Avoid long 'City, Country' strings; use country for country filters. For multiple metros, prefer location_or."New value: +"Text filter on job location strings (partial match). For metro-area or 'near me' intent, prefer near_lat + near_lng + radius_km (50–65 km typical) so results are not tied to one city spelling. Use location only when you cannot geocode, or as a fallback. Avoid long 'City, Country' strings; use country for country filters. For multiple metros, prefer location_or."
  10. Changed1 schema field changed
    • changedInput schema / properties / location / description
      Previous value: -"Text filter on job location strings (partial match). For metro-area or 'near me' intent, prefer near_lat + near_lng + radius_km (50–65 km typical) so results are not tied to one city spelling. Use location only when you cannot geocode, or as a fallback. Avoid long 'City, Country' strings; use country for country filters. For multiple metros, prefer location_or."New value: +"Display name of the place (e.g. 'San Francisco, CA'). When near_lat/near_lng are set this is only a label and is NOT used as a text filter. Otherwise a text filter on job location strings (partial match). For metro-area or 'near me' intent, prefer near_lat + near_lng + radius_km (50–65 km typical) so results are not tied to one city spelling. Use location only when you cannot geocode, or as a fallback. Avoid long 'City, Country' strings; use country for country filters. For multiple metros, prefer location_or."
  11. First observed

TDQS

A4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover safety (readOnly, idempotent, non-destructive, open world), and the description adds real behavior beyond them: endless scroll ordering, the related/country/world fallback chain, anonymous search with no OAuth, a hard 30-day recency ceiling and 7-day default. It does not contradict any annotation, though the fallback explanation is verbose enough to dilute the signal.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Roughly 900 words for a search tool, with the same rules repeated: the leading-dash negative convention is explained three times, company slug behavior twice, and cursor pagination twice. Instructions are front-loaded only for the first sentence; the rest is an unordered stream mixing parameter rules, post-search behavior, and UI caveats.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 20-parameter search with an output schema, the description covers the edge cases an agent would otherwise get wrong: multi-metro handling, remote-only searches, visa sponsorship defaults, recency mapping, and what to do when filters return nothing. Nothing essential to calling the tool correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the schema already documents slugs, negative dashes, enum values, and posted_within_days mappings, so the description largely restates structured data. It adds only light guidance beyond the schema: 'radius_km 25-50 for a city' (which slightly conflicts with the schema's 50-65 typical) and the advice to keep query to title text only. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a concrete verb and resource: 'Shows Worklittle job cards for a place and an optional role,' which lets an agent separate it from get_job_details and search_companies. The core statement is clear, but it is buried under several hundred words of operational instructions, so the tool's identity has to be extracted rather than read off the top.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to call it ('Call it whenever they want Worklittle jobs'), when not to ('Do not call get_account, apply, or ask the user to Connect'), and routes between alternatives: near_lat/near_lng vs location vs location_or, remote:true vs place fields, country for country filters. It also warns to prefer no filters and to retry a broader query on 0 results.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources