Skip to main content
Glama
460,228 tools. Updated 2026-08-18 00:53

"A tool for finding job openings and employment opportunities" matching MCP tools:

  • Get employment projections and career outlook for an O*NET occupation. Returns projected job growth rate, employment numbers, projected openings, and an outlook summary (bright, average, or below average). Args: soc_code: The O*NET-SOC code (e.g. '15-1252.00' for Software Developers).
    Connector
  • Assess labor market health for housing demand. Returns employment, construction jobs, residential building employment, unemployment rate, and job openings.
    Connector
  • Inspect the full chain tree for any job — rooted at the given job_id, walking down through every handoff and askAnySkill subcall. Use when a chain has already run and you want to analyze the structure: which skill called which, how deep the call tree went, which tool inside which job invoked which sub-tool. The two main shapes: • response.chain.chainJobs[] — one entry per job in the chain. Fields: jobId, skill, status, iteration, depth (0 = root, +1 per askAnySkill subcall hop), relation ('root' | 'subcall' | 'handoff'), parentJobId, parentSkill, goal. • response.chain.executionSteps[] — every tool call across all chain jobs, tagged with _skill, _jobId, _depth (= job depth), _relation, _parentSkill, _parentJobId, _toolDepth (tool-in-tool nesting via opId/parentOpId). Differs from ateam_test_status by purpose: status is for live polling of a job you just kicked off; get_chain is for post-hoc tree analysis (debugging multi-skill flows, regression testing, comparing two runs). Auth: forwards your authed api_key. Tenant scoped by the key itself. Actor scoping: you can only inspect chains rooted at jobs your actor has access to.
    Connector
  • Query verified U.S. employment, establishments, and wages — total and by industry (data centers, semiconductors, construction, retail, accommodation, food service) — for any county, state, or the nation, from the U.S. Bureau of Labor Statistics' Quarterly Census of Employment and Wages (QCEW). Use this for two families of questions: (1) "how many people work in / how many establishments / what wages in data centers or chip fabs" — INDUSTRY employment, not an "AI jobs" count; and (2) the place-based question — "what happened to a county's employment, wages, construction, or local economy (e.g. during and after a data-center / fab buildout)": total covered employment plus the buildout-phase and induced-sector series for every US county, quarterly since 2014. Filter by `industry_code` — each code lives at ONE aggregation depth, shown here with its agglvl codes (national/state/county): "10" Total, all industries — every covered job (agglvl 10/50/70 = all ownerships combined; 11/51/71 = split by ownership) "23" Construction (sector; 14/54/74) "44-45" Retail trade (sector; 14/54/74) "721" Accommodation (3-digit; 15/55/75) "722" Food services & drinking places (3-digit; 15/55/75) "236220" Commercial & institutional building construction (6-digit; 18/58/78) "518210" Computing infrastructure / data processing / web hosting — the data-center industry (6-digit; 18/58/78) "334413" Semiconductor & related device manufacturing (6-digit; 18/58/78) `agglvl`'s first digit is geography (1 national / 5 state / 7 county); pick ONE industry_code and the matching agglvl for its depth to get a clean additive scope. Also filter by `own_code` ("5" = Private — the usual one; "1"/"2"/"3" = federal/state/local government; "0" = Total Covered, only on industry "10"), geography (`state` USPS e.g. "VA", `county_fips` 5-digit e.g. "51107" Loudoun County, or `area_fips`), and time (`year`, `qtr` "1"-"4", the `quarter` ISO first-of-quarter e.g. "2025-10-01", or a `quarter_from`/`quarter_to` range). Group by any of `industry`, `industry_code`, `ownership`, `own_code`, `state`, `county_fips`, `agglvl`, `year`, `qtr`, or `quarter`. Pass each parameter as a top-level key of `params` (flat — not nested under a `filter`/`where` key). Examples: `{"industry_code": "518210", "own_code": "5", "agglvl": "18", "quarter": "2025-10-01"}` — the national private data-center-industry figure; `{"industry_code": "10", "own_code": "0", "agglvl": "70", "county_fips": "51117", "group_by": ["quarter"], "quarter_from": "2014-01-01"}` — total employment in Mecklenburg County VA, quarterly (the "did the buildout move the county" series); swap `"industry_code": "23", "own_code": "5", "agglvl": "74"` for its construction sector. Returns JSON aggregates with citations and optional row-level records when `include_records` is true — every value cites the exact BLS file, row, and quarter. Measures: `qtrly_estabs` (establishments), `month1_emplvl`/`month2_emplvl`/`month3_emplvl` (employment in each month of the quarter — intra-quarter SNAPSHOTS; average them for a quarterly figure, never sum them), `total_qtrly_wages` ($), and `avg_wkly_wage` ($, on detail records). Industry series are DISTINCT and NESTED: "10" contains the sectors, "23" contains "236220" — never sum across industry codes (each depth has its own agglvl, so a mixed-depth scope draws the `qcew_hierarchy` note). WHERE JOBS ARE COUNTED: at the employer's ESTABLISHMENT, not the work site. A construction crew building in county X for a contractor based in county Y counts in county Y — so a county's construction series understates on-site buildout labor staffed by outside contractors. SUPPRESSION: BLS withholds a confidential (small county × industry) cell by zeroing its employment and wages and marking `disclosure_code` "N" (or "-"). Those are served as NULL (absent), never as zero — the establishment count is still shown. Roughly half of county × data-center cells are withheld ("10" and sector-level cells are rarely withheld); an absent value means "BLS withheld it," not "no jobs." A scope containing withheld cells returns a `qcew_suppression` note counting them: sums skip the NULLs, so summed employment/wages UNDERCOUNT — for a state or national figure use BLS's own row at that level (agglvl 5x/1x) instead of summing finer cells. Data is quarterly back to 2014 Q1, ~6-month lag (latest ≈ 2025 Q4). The response `as_of` is the release vintage; pin `as_of` to reproduce an earlier vintage. NAICS VINTAGE: each year is served exactly as BLS coded it — 2014-2021 under NAICS 2017, 2022Q1-forward under NAICS 2022; BLS never recodes history. The 2022 revision REDEFINED 518210 (retitled to "computing infrastructure providers…"), so a 518210 series crossing 2022Q1 mixes two definitions — a level shift at that boundary (e.g. Loudoun County VA: −45% in one quarter) is establishment reclassification, not jobs lost. Compare 518210 within one vintage side of 2022Q1, or say so when crossing it. NOT additive across hierarchy or time: counts and employment are additive across distinct AREAS within ONE `agglvl` + ONE `own_code` + ONE quarter (e.g. all counties in a state). They are NOT additive across geographic levels (national already contains states/counties — a `qcew_hierarchy` note flags it), across industry depths ("10" contains the sectors and 6-digit codes), across ownership totals ("0"/"8" contain their components), or across QUARTERS (employment is a per-quarter stock — a `qcew_period` note flags it; quarterly wages, by contrast, sum across quarters into an annual bill). Filter or group_by to avoid double-counting. Does not determine "AI jobs" or a data-center-only headcount (NAICS 518210 is the broader computing-infrastructure / hosting industry), jobs at the work SITE (counted at the employer's establishment — see above), a definition-constant 518210 series across 2022Q1 (the NAICS vintage break — see above), industries beyond the eight pinned series (e.g. electrical contractors 238210 — largely absent/suppressed at county grain), employment for a withheld cell (served absent), occupation or job-title detail (QCEW is industry, not occupation), which company employs (no employer breakdown), or MSA / metro figures (national / state / county only).
    Connector
  • Record payment for an ACCEPTED job. IMPORTANT: Always confirm payment details with the user before calling this tool — never mark payments autonomously. Job must be in ACCEPTED status (use get_job_status to check). Crypto payments (usdc, eth, sol): provide tx hash + network → verified on-chain instantly, job moves to PAID. Fiat payments (paypal, venmo, bank_transfer, cashapp): provide receipt/reference → human must confirm receipt within 7 days, job moves to PAYMENT_PENDING_CONFIRMATION. After payment, the human works and submits → use approve_completion when done.
    Connector
  • Saves a job posting found anywhere on the open web into the user's tracker. For jobs that came from jobs_search results, tracker_add (which takes a job_id) is the right tool instead. A job seen elsewhere in the conversation needs no prior jobs_search call — its URL and details from the conversation are sufficient input. `url`, `company_name`, `title_name`, `location_name`, and `description` identify the posting and are the only required fields. Every structured fact field (salary, dates, employment type, education, experience) is optional: a fact the source does not state is simply omitted (or null), and FoundRole's own extractors derive missing salary, employment, work-arrangement, education, experience, skills, benefits, and bonuses from the description. A save never waits on facts the source did not provide. The optional `client_extraction` object carries evidence-backed skills, technology, benefits, bonuses, seniority, industry, management, clearance, visa, and remote-scope labels when source excerpts for them exist; FoundRole validates and stores those labels separately. Fields: - `url`: the job posting's direct URL (required; not a company homepage) - `company_name`: company name (required) - `title_name`: job title (required) - `location_name`: location, e.g. "New York, NY" (required) - `description`: the posting's description from the source result; a short summary is acceptable (required) - `salary_min_value` / `salary_max_value`: salary range bounds (numbers) - `salary_value`: a single salary figure when there is no range (number) - `posted_at`: ISO 8601 posting date - `salary_currency`: ISO 4217 currency code - `salary_type`: one of year, month, week, day, hour - `employment_type`: array of full_time, part_time, contractor, temporary, intern, volunteer, per_diem, other - `work_location_type`: one of on_site, remote, hybrid - `education_requirements`: array of no_requirements, high_school, associate_degree, bachelor_degree, professional_certificate, postgraduate_degree - `experience_months`: minimum required experience in months (number) - `client_extraction`: evidence-backed extraction object; fields without source evidence are omitted - `status`: initial tracking status (saved, applied, interviewing, offered, archived); defaults to "saved" - `sub_status`: sub-status within the main status: saved: interested, researching_company, preparing_application, ready_to_apply; applied: application_submitted, followed_up; interviewing: interview_scheduled, phone_screen, technical, onsite, final_round, pending_feedback; offered: negotiating, considering, offer_received, accepted; archived: ghosted, rejected_by_company, withdrawn_by_candidate, not_interested, employed_by_this_company, employed_by_another_company - `notes`: notes about the job Returns the tracked job. Repeated saves return the existing tracked job.
    Connector

Matching MCP Servers

  • A
    license
    -
    quality
    A
    maintenance
    MCP server that exposes job search data from multiple boards, enabling clients to query and manage job listings via natural language.
    7
    MIT

Matching MCP Connectors

  • Checks a generation job started by `picsart_generate` with `async: true`. Widget-facing: widgets poll this every few seconds with the returned job handle; assistants normally call `picsart_generate` synchronously and never need this tool. While running it returns `{ status: "ACCEPTED"|"IN_PROGRESS", progress?: { percent, estimatedSecondsLeft } }`. Once finished it returns the same media payload `picsart_generate` would have returned (`{ status: "COMPLETED", assets, results, url, ... }`), or an error for FAILED/CANCELED jobs. Requires Authorization: Bearer <picsart_token>.
    Connector
  • Get the status or result of a job started by deep_research, translate_pdf, or make_slides. Poll every 15-30 seconds until status is "done" or "error". While work is pending, follow retry_after_seconds and next_action; when complete, prefer structured_result when present. Example — GET https://ainetcafe.com/t/check_job?job_id=<id-from-a-job-tool>
    Connector
  • Retrieve the name and description of the company behind a job, by job ID. Use this tool when users want more detail about a company than search_jobs/get_job_details return (e.g. after finding a job and wanting to know more about the company that posted it). DO NOT use for: searching/discovering companies or jobs by keyword (use search_jobs instead). LLM USAGE INSTRUCTIONS: - The typical flow is: search_jobs to find jobs -> user picks one -> offer to look up the company -> if the user agrees, call this tool with that same job_id (the same guid used for get_job_details; no separate lookup step is needed first). - Do not call this automatically right after get_job_details; ask the user first unless they already explicitly asked for company details. - Not every company has published an employer branding profile, and some profiles are marked not visible by the company. When that happens this tool does NOT raise — it returns a Company with `message` set and empty name/desc. Relay that message to the user (e.g. "Looks like that company hasn't published a public profile.") rather than treating it as an error. Args: job_id: The unique identifier of the job whose company to look up (required). This must be the job's `guid` field from a search_jobs result, NOT its `id` field — `id` is a different, internal identifier that this tool does not accept. Returns: Company: Contains: - name: The company name (empty if message is set) - desc: The company description (empty if message is set) - message: Set instead of name/desc when there is no visible company profile to show; None when name/desc are populated Raises: Exception: If the job is not found, an API call itself fails (network error, non-200 response, GraphQL errors), or input validation errors occur
    Connector
  • Get the status or result of a job started by deep_research, translate_pdf, or make_slides. Poll every 15-30 seconds until status is "done" or "error". While work is pending, follow retry_after_seconds and next_action; when complete, prefer structured_result when present. Example — GET https://ainetcafe.com/t/check_job?job_id=<id-from-a-job-tool>
    Connector
  • USE ONLY when the user explicitly asks to check whether their LLM brand Discoverability Assessment is ready. Part of the flow started by `start_discoverability_assessment`. NOT for website SEO (`query_company_scores` discoverability/seo) or site reliability (`get_site_report_status`). Checks the status of a Discoverability Assessment job queued by `start_discoverability_assessment`. Call this tool ONLY when the user explicitly asks to check status — never poll automatically or in a loop. REQUIRED INPUT: the `JobId` returned by `start_discoverability_assessment`. If the user did not provide it and it is not in conversation context, ask them or re-run `start_discoverability_assessment`. STATUS VALUES (from the API): - 201 — job is queued; tell the user it is still waiting and they can ask again later. - 202 — job is in progress; tell the user it is still running and they can ask again later. - 200 — job finished; `ReportId` is populated and `IsFinished = true`. Call `get_discoverability_assessment` with the `ReportId` to retrieve the full analysis and human-friendly summary. - 400 — bad request (invalid jobId, etc.); do not retry blindly — verify the jobId. - 500 — job errored out; surface the API message to the user. DO NOT POLL: After calling this tool, if status is 201 or 202, report the current state to the user and stop. Do NOT call this tool again unless the user explicitly asks to check status. Do not call `get_discoverability_assessment` until `IsFinished = true` and a `ReportId` is available.
    Connector
  • Get the status or result of a job started by deep_research, translate_pdf, or make_slides. Poll every 15-30 seconds until status is "done" or "error". While work is pending, follow retry_after_seconds and next_action; when complete, prefer structured_result when present. Example — GET https://ainetcafe.com/t/check_job?job_id=<id-from-a-job-tool>
    Connector
  • Get the status or result of a job started by deep_research, translate_pdf, or make_slides. Poll every 15-30 seconds until status is "done" or "error". While work is pending, follow retry_after_seconds and next_action; when complete, prefer structured_result when present. Example — GET https://ainetcafe.com/t/check_job?job_id=<id-from-a-job-tool>
    Connector
  • Latest U.S. labour-market data from the Bureau of Labor Statistics, with the headline changes computed. Returns the unemployment rate, labour force participation rate, total nonfarm payrolls, the month-over-month change in payrolls (the "jobs added" number that leads the Employment Situation report), average hourly earnings, and year-over-year wage growth. All series are seasonally adjusted. BLS publishes levels; the month-over-month and year-over-year changes are computed here. When to use: reading the state of the labour market, wage-inflation context, or Fed-policy reasoning. When NOT to use: you need state or metro level detail, industry breakdowns, or JOLTS openings and quits. Args: none. Returns structuredContent: { "asOf": "2026-07", "periodName": "July 2026", "unemploymentRate": 4.1, "participationRate": 62.4, "nonfarmPayrolls": 158858, "payrollsChange": 73, "avgHourlyEarnings": 37.62, "earningsYoyPercent": 3.8, "source": "https://www.bls.gov/ces/" } Payrolls are in thousands of jobs, so payrollsChange 73 means +73,000 jobs on the month.
    Connector
  • Search 500+ quantum computing job listings using natural language. Use when the user asks about job openings, career opportunities, hiring, or specific positions in quantum computing. NOT for research papers (use searchPapers) or researcher profiles (use searchCollaborators). Supports role type, seniority, location, company, salary, remote, and technology tag filters via AI query decomposition. Limitations: quantum computing jobs only, last 90 days, max 20 results. Promoted listings appear first (marked). After finding jobs, suggest getJobDetails for full info. Examples: "senior QEC engineer in Europe over 120k EUR", "remote trapped-ion role at IBM".
    Connector
  • Upload JSON metadata to IPFS via Pinata and return the ipfs:// URI. Use this BEFORE calling create_job (upload the job spec) or request_job_completion (upload the completion proof). Requires a Pinata JWT — get one free at https://app.pinata.cloud/developers/api-keys. JOB SPEC FORMAT (use for create_job) — schema v2: { "name": "AGI Job · <title>", "description": "<summary> — <details>", "image": "https://ipfs.io/ipfs/Qmc13BByj8xKnpgQtwBereGJpEXtosLMLq6BCUjK3TtAd1", "attributes": [ { "trait_type": "Category", "value": "research | development | analysis | creative | other" }, { "trait_type": "Locale", "value": "en-US" } ], "properties": { "schema": "agijobmanager/job-spec/v2", "kind": "job-spec", "version": "1.0.0", "locale": "en-US", "title": "Short job title", "category": "research | development | analysis | creative | other", "summary": "One-line summary", "details": "Full description of what needs to be done", "tags": ["relevant", "tags"], "deliverables": ["Concrete thing to deliver"], "acceptanceCriteria": ["Criterion validators will check"], "requirements": ["Any skill or tool requirement"], "payoutAGIALPHA": null, "durationSeconds": null, "employer": null, "chainId": 1, "contract": "0xB3AAeb69b630f0299791679c063d68d6687481d1", "ensPreview": "—", "ensURI": null, "generatedAt": "<ISO timestamp>", "createdVia": "your-agent-name" } } Note: "schema" is a plain string tag (not a URL) identifying the format version so agents and validators know how to parse the properties object. COMPLETION FORMAT (use for request_job_completion): { "name": "AGI Job Completion · <job title>", "description": "Final completion package for Job <jobId>. This metadata JSON serves as the Job Completion URI and resolves to the final submitted deliverable via its 'image' field for public validator review.", "image": "ipfs://<CID of primary deliverable — any file type: PNG, TXT, PDF, JSON, etc. Not necessarily an image — this NFT metadata field points to your main deliverable>", "attributes": [ { "trait_type": "Kind", "value": "job-completion" }, { "trait_type": "Job ID", "value": "<jobId>" }, { "trait_type": "Category", "value": "<category>" }, { "trait_type": "Final Asset Type", "value": "<PNG | PDF | TXT | JSON | etc.>" }, { "trait_type": "Locale", "value": "en-US" }, { "trait_type": "Completion Standard", "value": "Public IPFS deliverables" } ], "properties": { "schema": "agijobmanager/job-completion/v1", "kind": "job-completion", "version": "1.0.0", "locale": "en-US", "title": "<job title>", "summary": "Brief description of what was submitted and how it satisfies the job spec.", "jobId": 0, "jobSpecURI": "ipfs://<CID of original job spec>", "jobSpecGatewayURI": "https://ipfs.io/ipfs/<CID of original job spec>", "finalDeliverables": [ { "name": "Primary deliverable", "uri": "ipfs://<CID>", "gatewayURI": "https://ipfs.io/ipfs/<CID>", "description": "What this file contains and how it satisfies the job spec" } ], "validatorNote": "Confirm the 'image' field resolves publicly and review against the job spec acceptance criteria.", "completionStatus": "submitted", "chainId": 1, "contract": "0xB3AAeb69b630f0299791679c063d68d6687481d1", "createdVia": "your-agent-name", "generatedAt": "<ISO timestamp>", "submissionType": "Job Completion URI" } }
    Connector
  • One-call TAM / market-size read for an industry (NAICS) in a US geography. Joins two independent federal sources that both count business activity by NAICS + area so each corroborates the other: US Census County Business Patterns (establishments, employment, annual payroll - needs a Census API key) and BLS QCEW (keyless: private establishment count, total wages, average annual pay, with employment implied from wages / avg pay). Returns the establishment count, employment, and a wage/payroll-based market-size anchor with the per-source evidence. Pass an 'industry' (e.g. 'restaurants', 'software publishers') or an explicit 'naics' code, and an optional 'state' or 'metro' (defaults to national). Market size here is the total annual wages/payroll paid in the industry+area - a concrete lower bound, NOT total revenue/receipts. A source that fails is noted, not fatal. Informational, not a guarantee.
    Connector
  • One-call 'can I hire this role here, and at what cost' read for an occupation in a US geography. Joins two independent federal sources: BLS OEWS (Occupational Employment and Wage Statistics, keyless) for the occupation's employment LEVEL and wage distribution (mean plus 10th / 50th-median / 90th annual percentiles) in the area, and US Census ACS labor-force context (civilian labor force and local unemployment rate - needs a Census API key) to band how TIGHT / BALANCED / SLACK the local hiring market is. Pass an 'occupation' (e.g. 'registered nurses', 'software developers') or an explicit 'soc_code' (e.g. '29-1141'), and an optional 'state' or 'metro' (defaults to national). Returns a readable brief with a headline (employment, median/mean wage, market tightness), the wage percentiles, and per-source evidence. The BLS OEWS leg is the core signal and is keyless; the Census leg degrades gracefully if no key is set. Informational, NOT a guarantee that a role can be filled at any given wage.
    Connector
  • Tailor a resume to a SPECIFIC job — TWO steps. STEP 1 (default; action omitted or 'prepare'): the server returns the job's full JD, its must-have skills/requirements, and the candidate's current resume, plus tailoring instructions. YOU (the model) then WRITE the tailored resume as JSON Resume, following the instructions — weave JD keywords into existing bullets only where the candidate genuinely has the experience, never fabricate experience/titles/dates/employers, keep all dates and company names, and flag any keyword you couldn't honestly add. STEP 2: call this tool again with action:'save', tailored_resume:<your JSON Resume>, and job_id — the server renders a PDF and saves it to the candidate's Workopia dashboard (requires sign-in). Use whenever the user references a specific job to tailor for: 'tailor for #1', 'for Morgan Stanley', 'tailor my resume for this role: <JD>'. Resolving job_id (same rules as job_detail_tool): from the most recent prior search/refine result — (a) numeric/ordinal → the Nth job; (b) company name → Company-field match; (c) role/title phrase → Job-Title match — then pass that job's **Job Id** value VERBATIM. Do NOT use placeholders like 'JOB_1' or '#1'. For STEP 1 supply ONE of job_id (preferred — server fetches the JD from Mongo) OR job_description, plus the candidate's resume via resume_text / resume_content / resume_data. For general 'improve my resume' (no specific job), do NOT call this tool — call resume_tool action=improve instead. Note: the tailored resume is written by your AI client's own model — the assistant you are already using — so it works out of the box with nothing to configure; Workopia runs no LLM of its own and never charges for the AI.
    Connector
  • Search jobs across 90+ countries by title, location, salary, remote/hybrid work mode, or employment type. Find roles in tech, finance, product, design, marketing, and every other vertical — aggregated from 1000+ ATS sources globally. Default action is search; use refine when the user asks for more matches or gives feedback on a prior result set; use save to bookmark a job for the signed-in user (requires OAuth). REFINE PROTOCOL (action=refine has THREE distinct modes): (1) Pure continuation / 'show me more' / 'next batch' / 'another set' / 'more like these': pass refine_recommendations.exclude_ids = the full array of **Job Id** values from the most recent search/refine result's content text (verbatim) + refine_recommendations.session_id = prior response's session_id if present. Server returns next 10 unique jobs. (2) 'Show me more like #N' / 'similar to the Atlassian one' / 'jobs like #2': pass refine_recommendations.liked_indexes = [N] (1-based position from prior numbered list) + exclude_ids + session_id. Equivalently you may pass refine_recommendations.liked_job_ids = [<that job's **Job Id** value verbatim>]. Server seeds the recommendation from that job's title/skills/company profile. (3) 'Less like #N' / 'no more N-style jobs' / 'avoid jobs like that': pass refine_recommendations.disliked_indexes = [N] (or disliked_job_ids = [<Job Id>]) + exclude_ids + session_id. Server suppresses similar jobs. All three modes: if you skip exclude_ids, the user sees duplicates — that's a failure. The handler layers exclude_ids with server-side AgentKit memory, so partial lists still work. NEVER invent 'JOB_1' / '#1' as job_id values — always use the real **Job Id** string from the prior result's content text. For detail requests (user asks about a specific job from the list, e.g. 'details for #1', 'show me this job', 'tell me more about <company>'), DO NOT call this tool — call job_detail_tool instead. That separate tool binds to the job-detail widget card so the full job card renders in chat. OUTPUT BEHAVIOR: Render the search results as a numbered markdown list, one line per job, in this exact compact format: `N. **[Job Title](View_Job_URL)** — Company · Location · Job Type · Compensation · Posted MMM DD`. Embed the View Job URL as a markdown link on the title (so the user can click to apply). Keep URLs intact — don't strip parameters. Skip a field entirely if it's missing — never print 'N/A' placeholders. The numbered list IS the canonical user-facing answer. REQUIRED follow-up: after the list, output EXACTLY these two sentences as two parallel questions (same pattern for action=search and action=refine): Sentence 1 — 'Would you like to see full details on any of these? Reply with the number (#1), the company name, or the role title.' Sentence 2 — 'Or would you like to refine the list — what should change (work mode, level, salary, sector)?' These two sentences must be separate and parallel; do NOT merge them into one 'detail ... or refine' clause (that buries the detail CTA). Both questions must be asked every time after a search or refine result. When the user replies referring to a specific job from the list, identify which job they mean and call job_detail_tool immediately. Identifying the job (use flexibly — users rarely type '#N' literally): (a) any numeric or ordinal reference ('#1', '1', 'first', 'the 1st', 'top one', 'job 3', 'the third') → the Nth job in your prior numbered list; (b) a company name, partial or full ('Morgan Stanley', 'Morstan', 'Capital One') → case-insensitive substring match on the Company field of the prior list, pick the first match; (c) a role/title phrase ('the analyst role', 'the credit risk one') → case-insensitive substring match on the Job Title field. If multiple jobs match, prefer the earliest. Only if no reasonable match exists, ask a one-line clarifying question. Then pass that job's **Job Id** value from the prior search result's content text VERBATIM as job_id to job_detail_tool / tailor_resume_tool / cover_letter_tool. Do NOT invent a placeholder like 'JOB_1' or '#1' — those are not server-valid IDs. For save, pass job_id + optional job_title/company/job_url in save_job. Put search fields in search_jobs or parameters; refine in refine_recommendations; save in save_job.
    Connector