company-jobs-feed

Official

by fairquery

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Re-check whether one job is still published (free)

jobs_check_open

Read-onlyIdempotent

Check whether a specific job is still open on Greenhouse, Lever, or Ashby before applying, alerting, or contacting about it.

Instructions

WHAT: Re-check ONE job on the employer's ATS right now and report open or closed. WHEN: Before applying, alerting or contacting about a specific job you got earlier (job_key or ats + slug + jobId). WHEN NOT: Listing jobs (jobs_get_board) or checking many jobs at once (jobs_search_companies with confirmOpen, paid). BEHAVIOR: Greenhouse, Lever: one GET to the documented per-job endpoint; HTTP 404 = closed. Ashby has no per-job endpoint, so the whole board is fetched once and searched for the id (method "board_listing"). "open" means currently published by the employer; it does not prove the role is still being filled. COST: Free. RETURNS: One item {type:"open_check", ats, slug, job_id, status: open | closed, method: detail_endpoint | board_listing, checked_at, source_url} or an error item (HOST_BLOCKED, NETWORK_ERROR: retryable). PARAMETERS: Give either jobKey alone, or ats + slug + jobId; jobKey wins when both are given. EXAMPLE: {"jobKey":"greenhouse:stripe:8172503"} -> {"status":"open","method":"detail_endpoint"}.

Input Schema

TableJSON Schema

Name	Required	Description
`ats`	No	Required. The applicant-tracking system hosting the board: "greenhouse" \| "lever" \| "ashby". Example: "ashby"
`slug`	No	Required. Board slug as it appears in the public board URL (case-insensitive): boards.greenhouse.io/<slug>, jobs.lever.co/<slug>, jobs.ashbyhq.com/<slug>. Example: "ramp" or "palantir"
`jobId`	No	Optional if jobKey is given. The ATS job id (job_id field). Example: "8172503"
`jobKey`	No	Optional if ats/slug/jobId are given. The job_key from a job row: "<ats>:<slug>:<job_id>". Example: "lever:palantir:10dfc8bc-99ad-4ca2-ab76-853cb90a92c2"

Output Schema

TableJSON Schema

Name	Required	Description
`meta`	No	Tool-specific context: board totals, request counts, cost notes
`count`	Yes	Number of items in this page
`items`	Yes	Result rows. Each has "type": "job" (job_key, title, company, locations, countries, remote, posted_at, verified_open_at, age_days, long_open, apply_url, source_url, ...), "board", "company", "seed_board", "open_check" or "error" (code, message, retryable)
`total`	Yes	Total items after filters, before paging
`offset`	Yes	Offset of the first item in this page
`hasMore`	Yes	True if more items exist after this page
`nextOffset`	Yes	Offset to pass for the next page, or null when done

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Oct 18, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Goes well beyond the annotations by explaining per-ATS mechanics (Greenhouse/Lever use a documented detail endpoint where HTTP 404 = closed; Ashby has no per-job endpoint so the board is fetched and searched, method 'board_listing'). It also flags retryable errors (HOST_BLOCKED, NETWORK_ERROR) and an important semantic caveat that 'open' means published, not actively hiring.

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?

Labeled WHAT/WHEN/WHEN NOT/BEHAVIOR/COST/RETURNS/PARAMETERS/EXAMPLE blocks are densely front-loaded with zero filler, and the one-line example anchors the calling convention. Verbose in raw length but every line carries unique information.

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?

Although an output schema exists (so returns need not be restated), the description nevertheless names the return fields and the failure modes, plus cost and ATS-specific behavior. An agent has everything needed to call it correctly and interpret the result.

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 each parameter is already documented, so the baseline is 3; the description earns above that by stating the either/or contract and the precedence rule ('jobKey wins when both are given'), which the schema does not express. It does not add format/syntax detail beyond the schema's examples.

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?

Starts with a specific verb+resource+scope ('Re-check ONE job on the employer's ATS right now') and explicitly reports the binary outcome (open/closed). It is immediately distinguishable from siblings like jobs_get_board and jobs_search_companies.

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?

Contains explicit WHEN ('before applying, alerting or contacting about a specific job you got earlier') and WHEN NOT sections that name the alternative tools and the condition that selects them (listing vs. bulk-checking with confirmOpen, paid). Nothing is left to inference.

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

Deploy Server