Skip to main content
Glama

Resume Booster Job Board

Read one job

get_job
Read-onlyIdempotent

Full detail for one job id (from search_jobs), with the complete description and when the board last read the employer's feed. A resumebooster.work/jobs?job= link's id is this argument (and fetch's and apply_myself's). For several ids at once use get_jobs. A dead id answers with what the board knows (closed, aged out, not found), never a stale card.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "get_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesA job id or its resumebooster.work job link.

Output Schema

NameRequiredDescriptionDefault
idNo
jobNo
noteNo
titleNo
agencyNo
closedNo
salaryNo
agedOutNo
companyNo
countryNo
siteUrlNo
applyUrlNo
locationNo
minYearsNo
notFoundNo
postedAtNo
workModeNo
applyFormNo
departmentNo
matchScopeNo
descriptionNo
recheckedAtNo
companyTokenNo
salaryPeriodNo
employmentTypeNo
experienceBandNo
salaryCurrencyNo
salaryMaxAnnualNo
salaryMinAnnualNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"The job id, e.g. 'greenhouse:acme:12345'."New value: +"A job id or its resumebooster.work job link."
  2. Changed39 schema fields changed
    • removedOutput schema / additionalProperties
      Removed value: -true
    • removedOutput schema / properties / agedOut / additionalProperties
      Removed value: -true
    • removedOutput schema / properties / agedOut / description
      Removed value: -"Past the 30-day freshness cap."
    • removedOutput schema / properties / agency / description
      Removed value: -"Present and true when the posting comes from a staffing/recruiting agency."
    • removedOutput schema / properties / agentReady
      Removed value: -{
      -  "description": "True when request_application can submit to this hiring system.",
      -  "type": "boolean"
      -}
    • addedOutput schema / properties / applyForm
      Added value: +{
      +  "type": "boolean"
      +}
    • changedOutput schema / properties / applyUrl / type
      Previous value: -[
      -  "string",
      -  "null"
      -]New value: +"string"
    • removedOutput schema / properties / category
      Removed value: -{
      -  "type": [
      -    "string",
      -    "null"
      -  ]
      -}
    • removedOutput schema / properties / closed / additionalProperties
      Removed value: -true
    • removedOutput schema / properties / closed / description
      Removed value: -"The board watched this posting come down: title, company, closedAt."
    • changedOutput schema / properties / company / type
      Previous value: -[
      -  "string",
      -  "null"
      -]New value: +"string"
    • removedOutput schema / properties / companyToken / description
      Removed value: -"The employer handle; pass it back in search_jobs `companies`."
    • changedOutput schema / properties / companyToken / type
      Previous value: -[
      -  "string",
      -  "null"
      -]New value: +"string"
    • removedOutput schema / properties / country / description
      Removed value: -"ISO-2."
    • changedOutput schema / properties / country / type
      Previous value: -[
      -  "string",
      -  "null"
      -]New value: +"string"
    • removedOutput schema / properties / department / description
      Removed value: -"The employer's own team name. ABSENT when the posting carries none."
    • removedOutput schema / properties / description / description
      Removed value: -"The posting's full text, truncated at 24,000 characters with a [truncated] marker."
    • changedOutput schema / properties / employmentType / type
      Previous value: -[
      -  "string",
      -  "null"
      -]New value: +"string"
    • removedOutput schema / properties / experienceBand / description
      Removed value: -"ABSENT when the posting's seniority could not be read."
    • removedOutput schema / properties / id / description
      Removed value: -"vendor:employer:externalId — the id every other tool takes."
    • removedOutput schema / properties / job / description
      Removed value: -"Present and null when there is no posting to return; read `closed` / `agedOut` / `notFound` beside it."
    • changedOutput schema / properties / location / type
      Previous value: -[
      -  "string",
      -  "null"
      -]New value: +"string"
    • removedOutput schema / properties / matchScope / description
      Removed value: -"Which part of the posting matched the query. ABSENT when the board's path did not say."
    • removedOutput schema / properties / minYears / description
      Removed value: -"Years of experience the posting asks for. ABSENT when it names none (most postings)."
    • removedOutput schema / properties / notFound / description
      Removed value: -"No posting with this id — never on this board, or gone long enough that nothing is remembered."
    • removedOutput schema / properties / postedAt / description
      Removed value: -"The employer's own date, ISO-8601. Null when the feed carries none — never the date we first saw it."
    • changedOutput schema / properties / postedAt / type
      Previous value: -[
      -  "string",
      -  "null"
      -]New value: +"string"
    • removedOutput schema / properties / recheckedAt / description
      Removed value: -"When the employer's feed was last fetched and still carried this employer's board."
    • removedOutput schema / properties / salary / description
      Removed value: -"The employer's own pay text, verbatim and unparsed."
    • changedOutput schema / properties / salary / type
      Previous value: -[
      -  "string",
      -  "null"
      -]New value: +"string"
    • removedOutput schema / properties / salaryCurrency / description
      Removed value: -"ISO-4217, as stated. ABSENT when unstated."
    • removedOutput schema / properties / salaryMaxAnnual / description
      Removed value: -"Annual USD-equivalent ceiling. ABSENT when unstated."
    • removedOutput schema / properties / salaryMinAnnual / description
      Removed value: -"Annual USD-equivalent floor, parsed by the board. ABSENT when the posting states no pay — absence is not zero."
    • removedOutput schema / properties / salaryPeriod / description
      Removed value: -"The period the employer stated: hour, month, year. ABSENT when unstated (most postings)."
    • removedOutput schema / properties / siteUrl / description
      Removed value: -"The posting's page on resumebooster.work."
    • changedOutput schema / properties / title / type
      Previous value: -[
      -  "string",
      -  "null"
      -]New value: +"string"
    • removedOutput schema / properties / workMode / description
      Removed 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."
    • changedOutput schema / properties / workMode / enum
      Previous value: -[
      -  "remote",
      -  "hybrid",
      -  "onsite",
      -  null
      -]New value: +[
      +  "remote",
      +  "hybrid",
      +  "onsite"
      +]
    • changedOutput schema / properties / workMode / type
      Previous value: -[
      -  "string",
      -  "null"
      -]New value: +"string"
  3. Changed4 schema fields changed
    • addedOutput schema / properties / matchScope
      Added value: +{
      +  "description": "Which part of the posting matched the query. ABSENT when the board's path did not say.",
      +  "enum": [
      +    "title",
      +    "description"
      +  ],
      +  "type": "string"
      +}
    • changedOutput schema / properties / minYears / description
      Previous value: -"Years of experience the posting asks for. ABSENT when it names none (~71%)."New value: +"Years of experience the posting asks for. ABSENT when it names none (most postings)."
    • changedOutput schema / properties / salaryPeriod / description
      Previous value: -"The period the employer stated: hour, month, year. ABSENT when unstated (~89% of the board)."New value: +"The period the employer stated: hour, month, year. ABSENT when unstated (most postings)."
    • addedOutput schema / properties / siteUrl
      Added value: +{
      +  "description": "The posting's page on resumebooster.work.",
      +  "type": "string"
      +}
  4. Changed1 schema field changed
    • 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."
  5. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive, so the safety profile is covered. The description adds behavior the annotations cannot: that the complete description and feed-freshness timestamp are included, and that a dead id returns a board-known status (closed, aged out, not found) rather than a stale card — exactly the failure-mode handling an agent needs.

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 tight sentences with the primary purpose front-loaded and no filler; each sentence carries distinct information (scope, freshness, id form, sibling routing, dead-id behavior). The possessive phrasing 'a ... link's id is this argument' is slightly awkward but still parses cleanly.

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?

An output schema exists, so return shape needn't be spelled out, and the description nonetheless covers the notable return traits (full description text, freshness timestamp, terminal statuses). For a single-parameter read tool this is complete enough to call correctly on the first try.

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?

Schema coverage is 100% and already states the id may be a job id or a resumebooster.work link, so the baseline is 3. The description earns above baseline by noting the link's id is the same argument accepted by fetch and apply_myself, which tells the agent it can reuse an id across calls rather than re-parsing links.

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?

Opens with a specific verb+resource promise: full detail for one job id, including the complete description and the board's last feed-read time. It explicitly contrasts with siblings ('For several ids at once use get_jobs') and ties itself to the search_jobs → get_job workflow, so an agent can distinguish it without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Clear context for use: an id sourced from search_jobs, or a resumebooster.work job link, and a named alternative (get_jobs) when several ids are needed. It stops short of saying when fetch or apply_myself should be used instead, but the routing guidance it does give is unambiguous.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.