company-jobs-feed

Official

by fairquery

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

List the verified starter boards (free, offline)

jobs_list_seed_boards

Read-onlyIdempotent

Lists verified company job boards from Greenhouse, Lever, and Ashby ATS APIs to pick companies to scan or find instantly resolvable boards.

Instructions

WHAT: List the bundled starter list of company job boards that Fairquery verified on their official ATS APIs (company, domain, ats, slug, verified_at, jobs_at_verification). WHEN: To pick companies to scan, or to know which names jobs_find_board resolves instantly. WHEN NOT: Live job data (jobs_get_board) or companies not in the list (jobs_find_board). The list is a starting point, not a global index of employers. BEHAVIOR: Offline: reads a static list compiled into the server; no network call. jobs_at_verification is a snapshot from verified_at and goes stale. COST: Free. RETURNS: Paged items {type:"seed_board", company, domain, ats, slug, verified_at, verified_by, jobs_at_verification}; meta.by_ats counts. PARAMETERS: ats narrows the list; omit it for all three systems. Feed ats + slug of any item straight into jobs_get_board. EXAMPLE: {"ats":"lever"} -> Palantir, Spotify, Zoox, Ro.

Input Schema

TableJSON Schema

Name	Required	Description
`ats`	No	Optional filter: "greenhouse" \| "lever" \| "ashby"; default all
`limit`	No	Optional page size, integer 1-500, default 50
`offset`	No	Optional items to skip, integer >= 0, default 0; pass nextOffset from the previous response

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

Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), but the description adds substantive behavior beyond them: offline static list with no network call, the free cost, and the staleness caveat that jobs_at_verification is a snapshot from verified_at. That staleness warning is exactly the kind of non-obvious trait that prevents misuse.

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 WHAT/WHEN/WHEN NOT/BEHAVIOR/COST/PARAMETERS/EXAMPLE structure is front-loaded and scannable, with no wasted clauses. The RETURNS block partially restates the output schema, which is the only mildly redundant element.

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 zero-required-parameter, read-only list tool with an output schema and full annotation coverage, the description supplies everything an agent needs: scope, exclusions, chaining guidance, cost, and the staleness caveat. Nothing material 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 the description adds genuine meaning: 'ats narrows the list; omit it for all three systems' clarifies the default behavior, and 'feed ats + slug of any item straight into jobs_get_board' documents the intended chaining usage that the schema cannot express.

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?

States a specific verb and resource ('List the bundled starter list of company job boards') plus the scope of what was verified (official ATS APIs) and the fields returned. It is immediately distinguishable from jobs_get_board (live data) and jobs_find_board (resolution of arbitrary names).

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?

Explicit WHEN ('to pick companies to scan, or to know which names jobs_find_board resolves instantly') and WHEN NOT ('live job data (jobs_get_board) or companies not in the list (jobs_find_board)'), naming both alternatives and the condition selecting each.

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

Deploy Server