company-jobs-feed

Official

by fairquery

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Find which ATS board a company uses (free)

jobs_find_board

Read-onlyIdempotent

Resolve a company name, domain, or careers URL to its public Greenhouse, Lever, or Ashby job board before fetching jobs.

Instructions

WHAT: Resolve a company name, domain or careers/board URL to its public job board(s) on Greenhouse, Lever or Ashby. WHEN: Before jobs_get_board when you only know the company ("Ramp", "sentry.io", "https://stripe.com/jobs"). WHEN NOT: You already have ats + slug (call jobs_get_board). For many companies plus their jobs in one step use jobs_search_companies (paid). It cannot find Workday, Workable, Recruitee or LinkedIn pages. BEHAVIOR: Runs on your machine. Order: board-URL parsing -> verified starter list -> the company's own website (only for a domain/URL input; robots.txt respected, <= 3 pages, private/internal IPs refused) -> at most 6 GETs against the documented ATS APIs with slug guesses. Stops at the first hit. Nothing is cached or stored. COST: Free. RETURNS: Items of type "board": {ats, slug, company, domain, via (board_url | seed_list | careers_page | slug_probe), confidence (high | medium), board_url}. A slug_probe hit is "medium": the slug exists but may belong to a different company with the same name; check the jobs or pass the URL from the careers page. meta.notes lists robots/blocked/network notes. PARAMETERS: company accepts three forms with different behavior: a board URL is parsed with no network call; a domain or https URL enables the careers-page step; a plain name only uses the starter list and slug probes. EXAMPLE: {"company":"ramp.com"} -> [{"ats":"ashby","slug":"ramp","via":"seed_list","confidence":"high"}].

Input Schema

TableJSON Schema

Name	Required	Description	Default
`company`	Yes	Required. Company name, domain or URL, 2-300 chars. Examples: "Ramp", "sentry.io", "https://jobs.lever.co/palantir"

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.7/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world, so the bar is lower, yet the description still adds substantial behavior: the resolution order, robots.txt respect, <=3 careers pages, refusal of private/internal IPs, at most 6 ATS API GETs, stopping at first hit, and no caching/storage. This is far beyond the annotations; the only omission is rate-limit/backoff behavior.

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?

Well front-loaded with labeled WHAT/WHEN/WHEN NOT sections and a concrete example, and every section carries information. It is long, and 'COST: Free' duplicates the title's '(free)' label, a minor redundancy in an otherwise dense block.

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?

Despite an output schema existing, the RETURNS section adds value the schema cannot: the 'via' enum values, the confidence semantics, and specifically that a slug_probe hit is only 'medium' and may be the wrong company. Combined with cost, network constraints and meta.notes, an agent has everything needed to call and interpret this tool.

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

Parameters5/5

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

Schema coverage is 100%, so a baseline of 3 applies, but the PARAMETERS section adds genuinely new meaning: the three accepted input forms (board URL, domain/URL, plain name) trigger different execution paths, which the schema's flat string description does not convey. The worked example further anchors expected input/output.

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 ('Resolve a company name, domain or careers/board URL to its public job board(s)') and immediately scopes it to Greenhouse/Lever/Ashby. It explicitly distinguishes itself from the siblings jobs_get_board and jobs_search_companies, so an agent can route 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 Guidelines5/5

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

The WHEN and WHEN NOT sections give explicit conditions and name the alternatives: use jobs_get_board when you already have ats+slug, jobs_search_companies for bulk paid lookups, and it states the ATSs it cannot find (Workday, Workable, Recruitee, LinkedIn). 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