work.resumebooster/jobs

Est-ce que work.resumebooster/jobs est sûr ?

Au dernier audit MCP Hub, le serveur MCP « work.resumebooster/jobs » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 15 outils

• application_status≈ 488 tokens

  Status of applications the key owner's agent has requested — queued, submitted, refused (with the refusing gate named), or failed. Needs a key or a sign-in.

  Paramètres, retour & exemple (1)

  Paramètres

  • limit · number · optionnel
    Most recent N, default 20, max 50.

  Exemple d'appel

  {"name": "application_status", "arguments": {"limit": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"fix": "texte", "error": "texte", "queued": [], "statusKey": {}, "applications": []}}

• board_stats≈ 500 tokens

  Live board statistics from cache (cheap to call): servable and tracked posting totals, the count of company job boards with open roles (boards, not employers — one employer can run several), the category set, freshness stamp. Answers with no key too, with a withKey block saying what a free key adds.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "board_stats", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"note": "texte", "withKey": {}, "categories": [], "refreshedAt": "texte", "trackedPostings": 1, "servablePostings": 1, "openCompanyBoards": 1, "freshnessWindowDays": 1, "openCompanyBoardsBasis": "texte"}}

• check_apply_support≈ 349 tokens

  Whether the apply agent can submit an application for this job on the user's behalf, and what that requires. Jobs on non-supported systems still return their direct applyUrl for the human to use. For whether THIS KEY may apply at all, call key_status — this tool answers about the job, not the key. Needs a key or a sign-in.

  Paramètres, retour & exemple (1)

  Paramètres

  • id · string · requis

  Exemple d'appel

  {"name": "check_apply_support", "arguments": {"id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"jobId": "texte", "vendor": "texte", "applyUrl": "texte", "agentReady": true, "requirements": []}}

• check_jobs_open≈ 401 tokens

  Are these postings still on the board? Answers up to 200 ids in one call — the tool for re-verifying a saved shortlist before acting on it, instead of spending a metered get_job per posting. Returns open:{id:boolean} plus the closed ids, and names the basis of the answer: it reads the board's index (a closed posting is one the employer's feed stopped listing), not the employer's site at this instant, and it is a weaker test than get_job's — read `basis` before reporting a posting as live to a person. Needs a key or a sign-in.

  Paramètres, retour & exemple (1)

  Paramètres

  • ids · array · requis
    Job ids from search_jobs. Up to 200 per call; anything past that is named in notChecked rather than silently dropped.

  Exemple d'appel

  {"name": "check_jobs_open", "arguments": {"ids": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"open": {}, "basis": "texte", "closed": [], "checked": 1, "openCount": 1, "notChecked": [], "closedCount": 1}}

• debug_search≈ 1965 tokens

  Explain WHY a search returns what it does — the board's own decision trace merged with the run's outcome. Shows the parsed query (terms, exclusions, intent-lifts, alias expansions), which filters were applied vs IGNORED and why, the route and retriever chosen, the ranking regime (ranked/ring-merged/deep-page and the seam), plus the real run's route, timings, count basis and any fallback. Use this when a search returns surprising, empty, or mis-ranked results — it turns 'why?' into one call. Takes the SAME arguments as search_jobs. Needs a key or a sign-in.

  Paramètres, retour & exemple (24)

  Paramètres

  • sort · string · optionnel · relevance | newest | salary
    Default relevance.
  • limit · number · optionnel
    Rows per page, 1-60. Default 20.
  • query · string · optionnel
    Search terms. Supports exclusions: 'engineer -senior'.
  • offset · number · optionnel
    Paging offset — pass back the previous response's nextOffset.
  • remote · boolean · optionnel
    Only remote-friendly roles.
  • vendor · string · optionnel
    Comma list of hiring-system vendors (greenhouse, lever, ashby, …), max 8. Not available here: usajobs, smartrecruiters — Two hiring systems are shown on resumebooster.work but not handed on by this connector: the U.S. federal job feed, whose terms of use forbid redistributing it as a data feed, and SmartRecruiters, withheld until SmartRecruiters (SAP) permits it. No tool here returns their rows; open the posting on the site instead. Naming one is refused rather than answered with an empty page.
  • country · string · optionnel
    ISO-2 codes, comma-separated, max 5. E.g. 'US,GB'.
  • category · string · optionnel
    Comma list of category slugs (see board_stats for the live set), max 3.
  • location · string · optionnel
    City/state/metro, e.g. 'texas', 'NYC', 'berlin'.
  • maxYears · number · optionnel
    Only roles asking for at most N years of experience.
  • payBasis · string · optionnel · hourly | salaried
    Restrict to hourly or salaried pay.
  • workMode · string · optionnel
    Comma list of: remote, hybrid, onsite.
  • companies · string · optionnel
    Scope to specific employers: a comma list of companyToken values from job cards (or from the site's employer pages). An employer the board does not carry simply matches nothing; tokens the board drops are named in ignoredFilters.
  • salaryMax · number · optionnel
    Annual USD-equivalent salary ceiling.
  • salaryMin · number · optionnel
    Annual USD-equivalent salary floor. Many postings state no comparable pay; the response's filterCoverage gives the live share this floor can see, dated by filterCoverageAt.
  • department · string · optionnel
    Substring match on the employer's own department/team text.
  • experience · string · optionnel
    Comma list of seniority bands the POSTING asks for: entry, mid, senior, expert. Rows whose band could not be read are excluded — use maxYears for the candidate's own side of the question.
  • maxAgeDays · number · optionnel
    Only postings from the last N days (1-30).
  • postedAfter · string · optionnel
    ISO-8601 instant; only postings the EMPLOYER dated after it. Undated rows fall out of this window (unlike maxAgeDays, which falls back to when the board first saw a posting), so this is the strict form of 'new'.
  • hasStatedPay · boolean · optionnel
    Only postings whose pay field carries a figure the employer published — hourly and per-shift rates included, read from the `salary` field. The response's filterCoverage gives the live share. Narrower than it sounds only for RANKING: salaryFloor compares an annualised figure in approximate US dollars, which fewer postings carry, so some rows this returns cannot be filtered by pay amount.
  • agentReadyOnly · boolean · optionnel
    Only jobs the apply agent can submit to on the user's behalf.
  • employmentType · string · optionnel
    Comma list of: full_time, part_time, contract, temporary, internship.
  • excludeAgencies · boolean · optionnel
    Hide postings from staffing/recruiting agencies (their job cards carry agency:true). Agencies are served by default; this is an opt-in narrowing.
  • includeUnstatedPay · boolean · optionnel
    WIDENS an active salaryMin/salaryMax band to also admit postings that state no pay at all. Inert with no band set (unpriced rows are already included). The response says salaryStatedOnly when a band is narrowing without it.

  Exemple d'appel

  {"name": "debug_search", "arguments": {"sort": "relevance", "limit": 1, "query": "texte", "offset": 1, "remote": true, "vendor": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"outcome": {}, "decision": {}}}

• employer_growth≈ 1139 tokens

  Did this employer's board serve more roles than it did 7 days earlier? One row per companyToken (up to 20 per call), judged by the board itself from our own daily observation and passed through untouched: grew, no-growth, or unknown — and unknown ALWAYS carries unknown_reason (a feed bigger than one visit can read, a board too new or too small for a rate, a gap in our own series, a pool that was replaced rather than grown…): an unknown is a reading we could not take, never a no. The bars the verdict uses: at least 10 roles served at the window's start; then BOTH at least 4 more roles AND at least 25% more, on a board tracked for at least 21 days, with every read in the window whole. Per BOARD (a vendor tenant), never summed across an employer's boards; more roles served is roles opened net of roles that came down — not a headcount and not a hire. This tool never ranks employers, and no list of growing employers exists here or anywhere on the board. Needs a key or a sign-in.

  Paramètres, retour & exemple (1)

  Paramètres

  • companyTokens · array · requis
    companyToken values from job cards or search_jobs. Up to 20; more is refused with the count named.

  Exemple d'appel

  {"name": "employer_growth", "arguments": {"companyTokens": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"bars": {}, "asked": 1, "basis": "texte", "employers": []}}

• employer_hiring_record≈ 1926 tokens

  For each employer handle (companyToken, up to 20 per call), that employer's own record on this board: open_roles now, closed_90d (takedown events we watched on this board in the last 90 days, re-lists excluded — one posting that came back and came down again counts each time), superseded_90d (the re-lists, a floor), the two medians from the employer's own stated dates (lower bounds), tracking_days (how long we have watched THIS board, capped at 90) and feed_total (what its feed advertised at the last check). A takedown is not a hire — a filled role, a cancelled one and a withdrawn one look identical from here — and it is a record of one BOARD, never summed across an employer's boards, never a headcount. A board with no closure observed answers record:'unknown' with the reason, never a verdict about the employer: on a board bigger than one visit can read, no closure is observable to us until we complete a provable full pass and then watch a role go after it, so silence there is about our instrument. Every row carries its basis. Every row also carries layoff_filing — the newest layoff filing joined to that employer by a hand-curated alias or an exact multi-token name match, a US state WARN notice or an SEC 8-K Item 2.05 disclosure, printed as a filing (filer verbatim, its dates with their bases, count, state or form, link), read hourly from SEC EDGAR and nightly from state notices, null when none qualifies within 90 days, and no part of record or any verdict; layoff_basis on the response says what it is and is not. Pair with employer_growth for the other half of what the site calls "Actively hiring". Needs a key or a sign-in.

  Paramètres, retour & exemple (1)

  Paramètres

  • companyTokens · array · requis
    companyToken values from job cards or search_jobs (a vendor tenant, e.g. 'acme' or 'gici~wd5~Careers'). Up to 20; more is refused with the count named.

  Exemple d'appel

  {"name": "employer_hiring_record", "arguments": {"companyTokens": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"asked": 1, "basis": "texte", "employers": [], "layoff_read": "texte", "window_days": 1, "layoff_basis": "texte"}}

• fetch≈ 378 tokens

  An ALIAS of get_job in the fixed shape ChatGPT's deep-research and company-knowledge connectors call: one id in (from search), {id,title,text,url,metadata} out. text is the posting's full description; metadata carries the job card's structured fields (pay, experience, location, workMode, postedAt, companyToken, agentReady). A dead id answers with what the board knows — a watched closure, an aged-out stub, or not found — in text and metadata, never a stale card. Any other client should call get_job.

  Paramètres, retour & exemple (1)

  Paramètres

  • id · string · requis
    A job id from search.

  Exemple d'appel

  {"name": "fetch", "arguments": {"id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"id": "texte", "url": "texte", "note": "texte", "text": "texte", "title": "texte", "metadata": {}}}

• fit_resume≈ 1716 tokens

  Score a résumé against open jobs, for an agent holding a CV: reads the occupation out of resumeText (or uses `query` if given), searches the board for it, and scores up to 20 results 0-100 with the matched and missing terms per job. PAID — needs a paid API key, exactly like POST /v1/fit on the data API, or a live Agent Pass or the Agent plan on the key's account; a free key gets an in-band refusal saying what opens it. A null fit means the posting has no stored description to score. Returns the terms it read from the CV so the agent can pick a different one and call again with `query`. Needs a key or a sign-in.

  Paramètres, retour & exemple (6)

  Paramètres

  • limit · integer · optionnel
    Jobs to score, 1-20 (default 20).
  • query · string · optionnel
    Optional job title to search instead of the one read from the résumé.
  • remote · boolean · optionnel
  • country · string · optionnel
  • location · string · optionnel
  • resumeText · string · requis
    The candidate's résumé as plain text (100+ characters).

  Exemple d'appel

  {"name": "fit_resume", "arguments": {"resumeText": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"jobs": [], "note": "texte", "query": "texte", "terms": [], "total": 1, "hasMore": true, "didYouMean": "texte", "nextOffset": 1, "relatedTotal": 1, "excludedTerms": [], "intentFilters": [], "relatedCapped": true}}

• get_job≈ 1112 tokens

  Full detail for one job id (from search_jobs), including the complete description text and when the employer's feed last confirmed it open. A resumebooster.work/jobs?job=<id> link's id is this argument (and fetch's, check_apply_support's and request_application's). For several ids at once, use get_jobs — it costs ONE call against the daily quota instead of one per posting. Needs a key or a sign-in. With neither, call fetch with the same id.

  Paramètres, retour & exemple (1)

  Paramètres

  • id · string · requis
    The job id, e.g. 'greenhouse:acme:12345'.

  Exemple d'appel

  {"name": "get_job", "arguments": {"id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"id": "texte", "job": "texte", "note": "texte", "title": "texte", "agency": true, "closed": {}, "salary": "texte", "agedOut": {}, "company": "texte", "country": "texte", "siteUrl": "texte", "applyUrl": "texte"}}

• get_jobs≈ 1184 tokens

  Full detail for up to 10 job ids in ONE call — the shortlist form of get_job. Each id answers with a card plus its description; ids that closed, aged out or were never on this board come back in `unavailable` with the reason named, so one dead id never costs you the other nine. Set includeDescription=false for cards and freshness only (much smaller, and no vendor fetch). Needs a key or a sign-in.

  Paramètres, retour & exemple (2)

  Paramètres

  • ids · array · requis
    Job ids from search_jobs. Up to 10 per call — each one is a separate detail read that may fetch the employer's page.
  • includeDescription · boolean · optionnel
    Default true. Descriptions are capped at 8,000 characters here; call get_job for the whole text of one.

  Exemple d'appel

  {"name": "get_jobs", "arguments": {"ids": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"jobs": [], "returned": 1, "requested": 1, "notFetched": [], "unavailable": []}}

• key_status≈ 1028 tokens

  What THIS key is and may do: tier, requests left this minute, calls left today (both including this call), whether fit_resume (and engine=ranked on the data API) answers on it, and whether the apply tools would — with any blocker named: account link, Agent plan or live pass, mandate, résumé on file. On an Agent Pass: when the clock ends and how many applications are left (a pass starts at the first call other than this one). Call it first in a keyed session, and after any 'quota' or 'rate' refusal. Needs a key or a sign-in.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "key_status", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"key": {}, "docs": "texte", "pass": {}, "rate": {}, "apply": {}, "quota": {}, "counted": "texte", "features": {}}}

• request_application≈ 782 tokens

  Ask the board's apply agent to submit an application to this job on behalf of the key's owner. Needs an account key (mint one at https://resumebooster.work/agents), an active Agent plan OR a live Agent Pass on the account, and a mandate set in Account — call key_status first: it says which of the three is missing, and on a pass how many applications and how much time are left. On a pass, only a job the agent can submit itself (agentReady true, which check_apply_support reports) uses an application; any other job is refused and nothing is spent. On the Agent plan nothing is counted, and such a job is prepared for the person to send. Every application passes the same gates as the signed-in flow, including the honesty classifier: answers are drawn from the owner's own profile and never invented. Ask the person for a yes on this specific job id before calling. Needs a key or a sign-in.

  Paramètres, retour & exemple (2)

  Paramètres

  • note · string · optionnel
    Optional note stored with the request (not sent to the employer).
  • jobId · string · requis
    The job id from search_jobs.

  Exemple d'appel

  {"name": "request_application", "arguments": {"jobId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"fix": "texte", "note": "texte", "error": "texte", "jobId": "texte", "title": "texte", "fitPct": 1, "company": "texte", "warning": "texte", "accepted": true, "refusedBy": "texte", "queueStatus": "texte", "alreadyQueued": true}}

• search≈ 822 tokens

  An ALIAS of search_jobs in the fixed shape ChatGPT's deep-research and company-knowledge connectors call: one query string in, {results:[{id,title,url}]} out. Every result's id is the job id fetch and every other tool take; url is the employer's own apply page when the board holds one, else the posting's page on the site. Same board, same ranking, same limit as an unkeyed search_jobs (10 rows); the disclosures ride beside the results. Any other client should call search_jobs, which takes every filter.

  Paramètres, retour & exemple (1)

  Paramètres

  • query · string · requis
    Free text — title, skills, a place, exclusions with a leading minus.

  Exemple d'appel

  {"name": "search", "arguments": {"query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"note": "texte", "total": 1, "hasMore": true, "results": [], "didYouMean": "texte", "nextOffset": 1, "relatedTotal": 1, "excludedTerms": [], "intentFilters": [], "relatedCapped": true, "filterCoverage": {}, "ignoredFilters": []}}

• search_jobs≈ 2505 tokens

  Search the live job board (postings pulled directly from employers' own hiring systems, 30-day freshness cap; board_stats carries the live totals). Returns compact job cards — including the board's own parsed pay (salaryMinAnnual/salaryMaxAnnual/salaryPeriod), experience band and minYears, so pay and seniority never have to be re-read out of prose — plus the board's honesty disclosures: exact totals when knowable (countUnavailable otherwise), filters it could not honour (ignoredFilters), words it read as filters (intentFilters), and spelling suggestions. Set agentReadyOnly=true to see only jobs the apply agent can submit to directly.

  Paramètres, retour & exemple (24)

  Paramètres

  • sort · string · optionnel · relevance | newest | salary
    Default relevance.
  • limit · number · optionnel
    Rows per page, 1-60. Default 20.
  • query · string · optionnel
    Search terms. Supports exclusions: 'engineer -senior'.
  • offset · number · optionnel
    Paging offset — pass back the previous response's nextOffset.
  • remote · boolean · optionnel
    Only remote-friendly roles.
  • vendor · string · optionnel
    Comma list of hiring-system vendors (greenhouse, lever, ashby, …), max 8. Not available here: usajobs, smartrecruiters — Two hiring systems are shown on resumebooster.work but not handed on by this connector: the U.S. federal job feed, whose terms of use forbid redistributing it as a data feed, and SmartRecruiters, withheld until SmartRecruiters (SAP) permits it. No tool here returns their rows; open the posting on the site instead. Naming one is refused rather than answered with an empty page.
  • country · string · optionnel
    ISO-2 codes, comma-separated, max 5. E.g. 'US,GB'.
  • category · string · optionnel
    Comma list of category slugs (see board_stats for the live set), max 3.
  • location · string · optionnel
    City/state/metro, e.g. 'texas', 'NYC', 'berlin'.
  • maxYears · number · optionnel
    Only roles asking for at most N years of experience.
  • payBasis · string · optionnel · hourly | salaried
    Restrict to hourly or salaried pay.
  • workMode · string · optionnel
    Comma list of: remote, hybrid, onsite.
  • companies · string · optionnel
    Scope to specific employers: a comma list of companyToken values from job cards (or from the site's employer pages). An employer the board does not carry simply matches nothing; tokens the board drops are named in ignoredFilters.
  • salaryMax · number · optionnel
    Annual USD-equivalent salary ceiling.
  • salaryMin · number · optionnel
    Annual USD-equivalent salary floor. Many postings state no comparable pay; the response's filterCoverage gives the live share this floor can see, dated by filterCoverageAt.
  • department · string · optionnel
    Substring match on the employer's own department/team text.
  • experience · string · optionnel
    Comma list of seniority bands the POSTING asks for: entry, mid, senior, expert. Rows whose band could not be read are excluded — use maxYears for the candidate's own side of the question.
  • maxAgeDays · number · optionnel
    Only postings from the last N days (1-30).
  • postedAfter · string · optionnel
    ISO-8601 instant; only postings the EMPLOYER dated after it. Undated rows fall out of this window (unlike maxAgeDays, which falls back to when the board first saw a posting), so this is the strict form of 'new'.
  • hasStatedPay · boolean · optionnel
    Only postings whose pay field carries a figure the employer published — hourly and per-shift rates included, read from the `salary` field. The response's filterCoverage gives the live share. Narrower than it sounds only for RANKING: salaryFloor compares an annualised figure in approximate US dollars, which fewer postings carry, so some rows this returns cannot be filtered by pay amount.
  • agentReadyOnly · boolean · optionnel
    Only jobs the apply agent can submit to on the user's behalf.
  • employmentType · string · optionnel
    Comma list of: full_time, part_time, contract, temporary, internship.
  • excludeAgencies · boolean · optionnel
    Hide postings from staffing/recruiting agencies (their job cards carry agency:true). Agencies are served by default; this is an opt-in narrowing.
  • includeUnstatedPay · boolean · optionnel
    WIDENS an active salaryMin/salaryMax band to also admit postings that state no pay at all. Inert with no band set (unpriced rows are already included). The response says salaryStatedOnly when a band is narrowing without it.

  Exemple d'appel

  {"name": "search_jobs", "arguments": {"sort": "relevance", "limit": 1, "query": "texte", "offset": 1, "remote": true, "vendor": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"jobs": [], "total": 1, "hasMore": true, "didYouMean": "texte", "nextOffset": 1, "relatedTotal": 1, "excludedTerms": [], "intentFilters": [], "relatedCapped": true, "filterCoverage": {}, "ignoredFilters": [], "agenciesExcluded": true}}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://bwhdazbotpblihdxcmho.supabase.co/functions/v1/agent-mcp