Resume Booster Job Board

Get one job

get_job

Read-onlyIdempotent

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

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	The job id, e.g. 'greenhouse:acme:12345'.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	No	vendor:employer:externalId — the id every other tool takes.
`job`	No	Present and null when there is no posting to return; read `closed` / `agedOut` / `notFound` beside it.
`note`	No
`title`	No
`agency`	No	Present and true when the posting comes from a staffing/recruiting agency.
`closed`	No	The board watched this posting come down: title, company, closedAt.
`salary`	No	The employer's own pay text, verbatim and unparsed.
`agedOut`	No	Past the 30-day freshness cap.
`company`	No
`country`	No	ISO-2.
`applyUrl`	No
`category`	No
`location`	No
`minYears`	No	Years of experience the posting asks for. ABSENT when it names none (~71%).
`notFound`	No	No posting with this id — never on this board, or gone long enough that nothing is remembered.
`postedAt`	No	The employer's own date, ISO-8601. Null when the feed carries none — never the date we first saw it.
`workMode`	No	The employer's own statement: the option they chose in their ATS, or their own words on the posting (title, location, department). null has THREE meanings: neither source says anything, the two disagree and the board refuses to choose, or the posting is older than the vendor field this board now reads. Never inferred from the description, and silence is never read as onsite.
`agentReady`	No	True when request_application can submit to this hiring system.
`department`	No	The employer's own team name. ABSENT when the posting carries none.
`description`	No	The posting's full text, truncated at 24,000 characters with a [truncated] marker.
`recheckedAt`	No	When the employer's feed was last fetched and still carried this employer's board.
`companyToken`	No	The employer handle; pass it back in search_jobs `companies`.
`salaryPeriod`	No	The period the employer stated: hour, month, year. ABSENT when unstated (~89% of the board).
`employmentType`	No
`experienceBand`	No	ABSENT when the posting's seniority could not be read.
`salaryCurrency`	No	ISO-4217, as stated. ABSENT when unstated.
`salaryMaxAnnual`	No	Annual USD-equivalent ceiling. ABSENT when unstated.
`salaryMinAnnual`	No	Annual USD-equivalent floor, parsed by the board. ABSENT when the posting states no pay — absence is not zero.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 27, 2026

changedOutput schema / properties / workMode / description

Previous value: -"Stated or inferred from title/location; null when neither says."New value: +"The employer's own statement: the option they chose in their ATS, or their own words on the posting (title, location, department). null has THREE meanings: neither source says anything, the two disagree and the board refuses to choose, or the posting is older than the vendor field this board now reads. Never inferred from the description, and silence is never read as onsite."

First observedSep 18, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive/openWorld, but the description adds non-obvious operational context: the auth precondition ('Needs a key or a sign-in'), the unauthenticated fallback, and the fact that each call consumes the daily quota. It also notes what the payload contains (complete description text, last-confirmed-open). Return format details are largely left to the output schema.

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

Conciseness4/5

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

Four dense sentences, front-loaded with the purpose and content, then the id provenance, then the alternative and auth path. No filler, though the parenthetical list of sibling tools sharing the id is slightly list-heavy.

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 one-param, output-schema-backed read tool, everything an agent needs is present: what it returns, how to obtain the id, the batch alternative, and the credential/fallback path. Nothing material is missing or deferred to guesswork.

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

Parameters4/5

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

With 100% schema coverage the baseline is 3, but the description adds real meaning: it tells the agent the id is the same value as the job=<id> query param in a resumebooster.work link and is shared by fetch, check_apply_support and request_application, plus where to obtain it (search_jobs). That cross-tool identity mapping is not in the schema.

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

Purpose5/5

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

States a specific verb+resource ('Full detail for one job id') and immediately qualifies scope and source ('from search_jobs'), which cleanly separates it from get_jobs (multiple ids) and fetch. An agent can pick it out without opening a schema.

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?

Explicit when-to-use (single id, need full description text), explicit alternative for the multi-case ('For several ids at once, use get_jobs — it costs ONE call'), and an explicit fallback when unauthenticated ('call fetch with the same id'). Routing is fully specified.

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

All Resume Booster Job Board tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.