Skip to main content
Glama
fairquery

company-jobs-feed

Official
by fairquery
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get live jobs from one ATS board (free)

jobs_get_board
Read-onlyIdempotent

Fetch live job openings from one company's Greenhouse, Lever, or Ashby board, then normalize and filter results locally.

Instructions

WHAT: Fetch every job currently published on ONE company board from its official public ATS API (Greenhouse, Lever or Ashby), normalize it and filter it locally. WHEN: You know the board (ats + slug), e.g. from jobs_find_board or a careers-page link, and want its live openings now. WHEN NOT: Many companies at once, history (new/closed/reposted since last run), or careers-page discovery at scale: use jobs_search_companies (paid). Unknown board: use jobs_find_board first. SmartRecruiters, LinkedIn, Workday, Workable and Recruitee are not supported and never contacted. BEHAVIOR: Runs on your machine; one GET to the documented API host only (very large Greenhouse boards: a second, lighter GET). No token, nothing stored, no history: first_seen_at = now and change = null. Any HTTP 403/429 stops that host for the session (kill switch, HOST_BLOCKED error). Lever requests are spaced 1 s apart (its robots.txt Crawl-delay). COST: Free. RETURNS: Paged job rows: job_key, title, company, department, team, locations, countries (+country_basis), remote (+remote_basis), workplace_type, employment_type, compensation (only when the ATS publishes it), posted_at (ATS date or null, never guessed), age_days + age_basis, long_open, verified_open_at, apply_url, job_url, source_url, fingerprint. meta: jobs_total on the board, jobs_matched, requests, complete. PARAMETERS: All filters are AND-ed; values inside one filter are OR-ed. titleIncludes/titleExcludes match whole words ("engineer" does not match "Engineering"). countries uses the ATS's structured country where present (Lever, Ashby) and a place-name list otherwise; rows without any country are dropped when countries is set. postedWithinDays drops rows with posted_at = null. Paging re-fetches the board, so pages from different calls can shift if the employer edits the board in between. EXAMPLE: {"ats":"ashby","slug":"ramp","titleIncludes":["engineer"],"remote":"only"} -> remote engineering roles at Ramp with salary ranges.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
atsYesRequired. The applicant-tracking system hosting the board: "greenhouse" | "lever" | "ashby". Example: "ashby"
slugYesRequired. 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"
limitNoOptional page size, integer 1-500, default 50
offsetNoOptional items to skip, integer >= 0, default 0; pass nextOffset from the previous response
remoteNoOptional, "any" | "only" | "exclude", default "any"
countriesNoOptional ISO-3166 alpha-2 codes, any-of, case-insensitive. Example: ["US","DE"]
locationsNoOptional, 0-50 strings, any-of. Substring match on location text; "remote" also matches ATS remote flags. Example: ["new york","berlin"]
longOpenDaysNoOptional integer, default 60: rows older than this get long_open = true (a heuristic, not proof of a ghost job)
titleExcludesNoOptional, 0-50 strings, any-of. Drop titles containing any of these. Example: ["intern","manager"]
titleIncludesNoOptional, 0-50 strings, any-of. Keep titles containing any of these whole words/phrases, case-insensitive. Example: ["engineer","data scientist"]
postedWithinDaysNoOptional integer 1-3650: keep jobs whose ATS publish date is at most this many days old. Example: 14
includeDescriptionNoOptional boolean, default false. true adds description_text (plain text, <= 20,000 chars, e-mails/phones removed)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
metaNoTool-specific context: board totals, request counts, cost notes
countYesNumber of items in this page
itemsYesResult 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)
totalYesTotal items after filters, before paging
offsetYesOffset of the first item in this page
hasMoreYesTrue if more items exist after this page
nextOffsetYesOffset to pass for the next page, or null when done

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.8/5.0
Behavior5/5

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

Annotations cover the safety profile, but the description adds substantial context annotations cannot: local execution, one GET to a documented host, a 403/429 session kill-switch with HOST_BLOCKED, Lever's 1 s Crawl-delay spacing, no token/storage, and first_seen_at/change semantics. This is rich disclosure beyond the structured hints.

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?

Heavily structured and front-loaded with WHAT/WHEN/WHEN NOT, so an agent gets routing information immediately. It is dense and the RETURNS block partially restates fields that the output schema already carries, which is the main reason it is not a 5.

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 12-parameter read tool with full schema coverage and an output schema, this covers the remaining gaps: filter composition rules, paging volatility when the board is edited, supported/unsupported ATSs, and rate-limit behavior. Nothing needed 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?

Schema coverage is 100%, so the baseline is 3, but PARAMETERS adds cross-parameter semantics not present in any single schema field: filters are AND-ed while values within a filter are OR-ed, titleIncludes matches whole words, countries drops unmatched rows, and postedWithinDays drops null-dated rows. Only slight overlap with the schema's per-field docs, hence 4 rather than 5.

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 WHAT line names a specific verb+resource (fetch every job published on ONE company board from its official public ATS API) plus the scoping constraint (one board, supported ATS list). It explicitly distinguishes itself from jobs_search_companies (many companies/history) and jobs_find_board (board discovery).

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?

WHEN gives the precondition (you know ats + slug), WHEN NOT enumerates the alternatives and the exact tools to use instead (jobs_search_companies for scale/history, jobs_find_board for unknown boards), and it rules out unsupported ATSs explicitly.

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

Deploy Server

Other Tools