Skip to main content
Glama

get_job

Read-onlyIdempotent

Fetch complete details for one job by key or posting ID—posting text, pay sources, fit score, application status, contacts, duplicates, and staffing warnings—to evaluate and track it.

Instructions

Everything about one job, by key or posting id: the full posting text, pay, tracking (status, note, next step, follow-up), its fit score against the resume (score, must-haves met, gaps, and requirements: each requirement with its verdict, met/partial/not_met, and the resume's words backing it; scores saved before jobwatch kept these have none), people the user knows there plus a LinkedIn search for a referral, skills it asks for that the resume doesn't show, what was sent with the application, and candidate_home: the company's page where the person signs in to see the application's status (Workday only; each company has its own account). link_note, when set, says the board's hosted job pages are offline and where to apply instead (url is then the company's careers site, when the watchlist gives one). With no fit score, unscored_reason says why ({code, text}: no_text means it needs its posting, a link via mark_job(url=) or the text pasted; queued means it's in the page's background scorer's line; many_roles, a post listing several roles, is never scored; stale, an older scorer's score, is scored again only when asked). duplicate_of is the job already applied to, queued or skipped that this one is (maybe) the same opening as: key, title, status, date, why, strong (a shared req or posting id; false: the same title only, so check it's a different opening), reposted, and text, the warning to heed; null when there's none. Check it before drafting a referral request or an application. staffing_firm, when the posting is from a staffing or recruiting agency, is the warning to heed (ask the client's name, and full-time vs contract); null otherwise. pay_sources has one entry per pay source, in order: posted (the posting's range), levels (Levels.fyi), lca (H-1B filings), recruiter (what set_comp kept), glassdoor (only what the person typed in: never fetched) and ask (the base to ask for); each is {label, value, reason, blank, ...}: value is null when the source has nothing, and reason says why (blank is TBD when it will be known later, none or off). lca_pay, once jobwatch lca update has been run, is the base pay the company filed for H-1B hires in titles like this one (median, 25th-75th percentile, count, wage levels, examples; U.S. DOL LCA disclosures): base only, not total compensation. Use it to tailor a resume or decide whether to apply; for only what was sent use get_application_package, and for a call or interview use get_interview_prep.

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": {
      "key": "<key>"
    },
    "name": "get_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesThe job: its key as other tools return it (source:board:posting id, e.g. greenhouse:acme:4012345), just the posting id, or the company's name when that names one job (the one queued or applied to there). When it matches several, the error lists their keys.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A3.8/5.0
Behavior3/5

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

Beyond the readOnly/idempotent/non-destructive annotations, the description discloses genuinely useful behavior: multiple key matches produce an error listing candidate keys, candidate_home exists for Workday only with per-company accounts, and unscored_reason codes (no_text, queued, many_roles, stale) explain absent fit scores. However it never mentions response size or pagination despite promising a very large aggregate payload, which matters for a read that fans out across many sub-resources.

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

Conciseness2/5

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

One ~350-word run-on paragraph with deeply nested parentheses ("each is {label, value, reason, blank, ...}") and mid-sentence pivots such as "Use it to tailor a resume...; for only what was sent use...". The purpose is front-loaded, but the body is undifferentiated prose where field-level details belong in a structured or bulleted layout.

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?

No output schema exists, so the description carries the full burden of documenting return fields, and it does so exhaustively: pay_sources ordering and null semantics, lca_pay contents and its base-only caveat, duplicate_of subfields including the meaning of strong, link_note and staffing_firm warnings. For a single-parameter, read-only aggregate getter, nothing an agent needs to interpret the result is missing.

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

Parameters3/5

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

Schema coverage is 100% and the schema's key description already covers the three accepted forms (source:board:posting id, bare posting id, company name) and the multi-match error. The description adds only the passing hint that mark_job(url=) can supply posting text; it contributes no new meaning about the single parameter.

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 concrete verb and resource: "Everything about one job, by key or posting id," then enumerates the returned domains (posting text, pay, tracking, fit score, contacts, skill gaps, candidate_home). It also explicitly distinguishes itself from get_application_package and get_interview_prep, so an agent can separate it from siblings without opening schemas.

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?

Gives clear trigger conditions: "Check it before drafting a referral request or an application" and "Use it to tailor a resume or decide whether to apply," plus routing to get_application_package for sent materials and get_interview_prep for interviews. What's missing is a negative boundary (when this tool is the wrong starting point, e.g. browsing many jobs, which list_jobs would serve).

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