Skip to main content
Glama

Fairquery Agent Trust & Data Safety

by com.getfairquery
OverviewDiscussionsAdmin

Get live jobs from one ATS board (free)

jobs_get_board
Read-onlyIdempotent

WHAT: Fetch every job currently published on ONE company board from its official public ATS API (Greenhouse, Lever or Ashby) or from Personio's documented XML feed for an account you name, normalize it and filter it on this Worker. WHEN: You know the board (ats + slug), e.g. from jobs_find_board or a careers-page link, and want its live openings now. For Personio you already know the company subdomain. WHEN NOT: One known job's full detail (jobs_get_job). Many companies at once, history (new/closed/reposted since last run), or careers-page discovery at scale: use jobs_search_companies (paid). Unknown Greenhouse/Lever/Ashby board: use jobs_find_board first. Personio accounts are never discovered. SmartRecruiters, LinkedIn, Workday, Workable, Recruitee and Rippling are not supported and never contacted. BEHAVIOR: Runs on this Fairquery-hosted Worker (Cloudflare), not on the caller's machine; inputs leave the client. This Worker's code is designed not to store inputs or results. The slug is sent to the public ATS host in the requests below. Greenhouse, Lever and Ashby: one GET to the documented API host only (very large Greenhouse boards: a second, lighter GET). Personio: robots.txt, then GET https://{account}.jobs.personio.de/xml only (no other path, query or apply URL); all Personio accounts share one lane, one request at a time, at least 1.5 s apart. 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). A blocked Personio account does not block other accounts. Lever requests are spaced 1 s apart (its robots.txt Crawl-delay). COST: No APIFY_TOKEN, no billing. RETURNS: Paged "job" rows. compensation only when the ATS publishes it; posted_at is the ATS date or null (never guessed); age_basis says how age_days was derived. 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

NameRequiredDescriptionDefault
atsYesRequired. The applicant-tracking system hosting the board: "greenhouse" | "lever" | "ashby" | "personio". Personio is the company account you name, not a discovered board. 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}, or the Personio account in {account}.jobs.personio.de (letters, digits, hyphens; a dot is rejected). 1-100 chars. Example: "ramp" or "acme"
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

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 observed

TDQS

A5/5.0
Behavior5/5

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

Beyond the annotations, it discloses hosted Worker execution, input egress, no-storage design, per-host request behavior, Personio lane throttling, Lever Crawl-delay spacing, 403/429 kill-switch behavior, no-history semantics, and cost. These details materially help an agent understand safety, latency, and failure modes.

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?

The description is dense but well-structured with WHAT, WHEN, WHEN NOT, BEHAVIOR, COST, RETURNS, PARAMETERS, and EXAMPLE sections. For a 12-parameter tool with multiple ATS backends and operational caveats, the length is justified and front-loaded.

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?

It covers purpose, usage routing, supported and unsupported providers, behavioral constraints, request patterns, cost, return semantics, filter semantics, and an example. With annotations and an output schema already present, the description supplies everything an agent needs to select and call the tool correctly.

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 description coverage is 100%, but the description still adds meaningful semantics beyond the schema: filters are AND-ed while values within one filter are OR-ed, title matching uses whole words, country filtering can drop unknown-country rows, and postedWithinDays drops null posted_at rows. It also explains paging drift because pages re-fetch the board.

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 description states a specific verb and resource: fetch every currently published job from one named board via an official ATS API or Personio feed, normalize, and filter it. It explicitly covers supported ATS types and distinguishes itself from siblings such as jobs_get_job, jobs_find_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?

It provides explicit WHEN and WHEN NOT guidance, including the prerequisite that the ats and slug are already known. It names alternatives for single-job detail, multi-company/history search, unknown boards, and Personio discovery, and lists unsupported ATS providers.

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

All Fairquery Agent Trust & Data Safety toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources