Skip to main content
Glama
company-jobs-feed

company-jobs-feed

Official

List the verified starter boards (free, offline)

jobs_list_seed_boards
Read-onlyIdempotent

List bundled starter company job boards verified on official ATS APIs to pick employers to scan and resolve supported board names.

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: No APIFY_TOKEN, no billing. RETURNS: Paged "seed_board" rows in the fixed bundled order (grouped by ATS, so offsets are stable). PARAMETERS: ats narrows the list; omit it for all three systems. meta.by_ats always counts the whole list per ATS and ignores ats, so take paging totals from total. Feed ats + slug of any item straight into jobs_get_board. EXAMPLE: {"ats":"lever"} -> Palantir, Spotify, Zoox, Ro.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "jobs_list_seed_boards"
  }
}

Input Schema

NameRequiredDescriptionDefault
atsNoOptional filter: "greenhouse" | "lever" | "ashby"; default all
limitNoOptional page size, integer 1-500, default 100
offsetNoOptional items to skip, integer >= 0, default 0; pass nextOffset from the previous response

Output 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. Changed1 schema field changedv1.0.6
    • changedInput schema / properties / limit / description
      Previous value: -"Optional page size, integer 1-500, default 50"New value: +"Optional page size, integer 1-500, default 100"
  2. First observedv1.0.1

TDQS

A4.9/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds genuinely new traits: fully offline with no network call, static list compiled into the server, jobs_at_verification is a freshness snapshot that goes stale, and no APIFY_TOKEN/billing required. That is real behavioral context beyond the structured fields.

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 sections (WHAT/WHEN/WHEN NOT/BEHAVIOR/COST/RETURNS/PARAMETERS/EXAMPLE) are front-loaded with the highest-value routing information first. Dense but every block carries distinct content; no filler sentences.

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?

An output schema exists so return values need not be re-explained, and the description still adds the non-obvious paging caveat (stable offsets due to fixed bundled ATS-grouped order) and the downstream hand-off to jobs_get_board. Nothing an agent needs to call this 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 the description adds meaning not in the schema: meta.by_ats always counts the whole list and ignores the ats filter, so paging totals must come from total; and ats+slug of any row feeds directly into jobs_get_board. The example clarifying that ats='lever' yields a specific set is useful, though limit/offset semantics are left to the schema.

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 ... verified on their official ATS APIs') and names the exact sibling tools it is not (jobs_get_board, jobs_find_board). An agent can distinguish this from live-data siblings 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?

Explicit WHEN ('to pick companies to scan', 'to know which names jobs_find_board resolves instantly') and WHEN NOT (live data goes to jobs_get_board; unlisted companies go to jobs_find_board). It also frames the list's scope as 'a starting point, not a global index of employers', which prevents misuse.

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