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	Stated or inferred from title/location; null when neither says.
`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.

First observedSep 18, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already signal read-only, idempotent, non-destructive behavior. The description adds valuable context beyond those annotations: the exact output contents, the need for a key/sign-in, quota implications, and the fallback path to fetch when unauthenticated.

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

Conciseness5/5

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

Three dense sentences, each earning its place. The main purpose is front-loaded, and quota/auth/fallback details are grouped without redundancy.

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 simple one-parameter, read-only tool with an output schema, this description covers sources of the id, what the response contains, auth requirements, quota behavior, and alternatives. Nothing an agent needs to call it correctly is missing.

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?

The schema already fully documents the id parameter with an example. The description adds meaningful extra context by explaining that the argument is the same id found in resumobooster.work/jobs links and is shared with fetch, check_apply_support, and request_application.

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 and resource: returns full detail for one job id, including description text and feed confirmation time. It clearly distinguishes itself from get_jobs by focusing on a single id rather than many.

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 says when to use this tool (one job id), when to use the alternative instead (several ids -> get_jobs, saving quota), and what to do without auth (call fetch). This is actionable routing guidance.

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.