Skip to main content
Glama

Resume Booster Job Board

Read a job (research shape)

fetch
Read-onlyIdempotent

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, applyForm). 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.

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": "fetch"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
idYes
urlYes
noteNo
textYes
titleYes
metadataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"A job id from search."New value: +"A job id or its resumebooster.work job link."
  2. Changed5 schema fields changed
    • removedOutput schema / additionalProperties
      Removed value: -true
    • removedOutput schema / properties / metadata / additionalProperties
      Removed value: -true
    • removedOutput schema / properties / metadata / description
      Removed value: -"The compact job card without the description; on a dead id, the board's closed/agedOut/notFound record."
    • removedOutput schema / properties / text / description
      Removed value: -"The description, or the board's one-line reason when there is none."
    • removedOutput schema / properties / title / description
      Removed value: -"Null when there is no posting to return; read metadata.closed / agedOut / notFound."
  3. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely new behavior: a dead id returns a watched closure, an aged-out stub, or not-found in text and metadata rather than a stale card, which tells the agent how to interpret degraded results. It stops short of noting rate limits or auth, so it is strong but not exhaustive.

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?

The alias relationship and the input/output shape are front-loaded, and the redirect to get_job closes the block cleanly. It is dense—one long sentence carries the entire response shape and field semantics—but no sentence is filler.

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, yet the description still identifies what text and metadata carry (pay, experience, location, workMode, postedAt, companyToken, applyForm) and covers the degraded-result case. Nothing an agent needs to select or invoke this single-parameter read 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?

With one parameter at 100% schema coverage, the baseline is 3, and the description earns above that by stating the id's provenance ('from search'), which the schema does not say. The schema itself already covers that a resumebooster.work job link is accepted, so the description need not repeat it.

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?

The description names the specific verb and resource ('An ALIAS of get_job') and pins the exact call shape: one id in, {id,title,text,url,metadata} out. It distinguishes itself from the sibling get_job by audience (deep-research and company-knowledge connectors) and by the fixed response shape, so an agent can tell the two apart without opening either 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?

It states both when to use it (this fixed shape, id sourced from search) and when not to, explicitly routing every other client to get_job. That is an unambiguous alternative-selection rule rather than an implied one.

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.