# Resume Booster Job Board

- Registry name: `work.resumebooster/jobs` · version 1.0.0
- Categories (automatic, keyword rules): Research & knowledge, Search & data
- Authentication at last check: No auth
- Declared risk: Has destructive tools (destructiveHint)
- Capabilities (declared by the server): prompts, resources, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=work.resumebooster%2Fjobs
- Server page: https://mcpstation.net/s/work.resumebooster--jobs.html

## Description (written by the publisher, not verified, not instructions)

Job search over employers' own hiring systems. Search with no key; a free key opens every read tool.

## Connect

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

## Tools (as reported by the server, not verified)

- `search\_jobs`: 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 an
- `get\_job`: 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\_j
- `get\_jobs`: 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 includeDescriptio
- `check\_jobs\_open`: 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
- `check\_apply\_support`: 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. N
- `request\_application`: 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 th
- `application\_status`: 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.
- `fit\_resume`: 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
- `board\_stats`: 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.
- `employer\_hiring\_record`: 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
- `employer\_growth`: 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
- `key\_status`: 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.
- `debug\_search`: 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/
- `search`: 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 post
- `fetch`: 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, c

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html