Skip to main content
Glama

Ats Boards

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Ats Jobs

ats_jobs
Read-onlyIdempotent

Fetch normalized job postings from a PUBLIC ATS board you already have the ats + board_token for (use ats_detect or ats_company_jobs if you only have a domain). Returns {found:false, reason:"board_not_found"} for an unknown board — never an empty jobs[] for that case. Lever/Ashby/BambooHR/Recruitee/Teamtailor/Breezy DO distinguish a real zero-job board (found:true, jobs:[]) from an unknown one; SmartRecruiters cannot (ambiguous:true); Pinpoint and iCIMS have not had a confirmed-empty real board observed live, so a 0-job result from those two is NOT independently confirmed to mean "real board, no jobs" versus a mis-detected token. Workday board_token is ".wd/" (e.g. "workday.wd5/Workday"); its response states capped:true if your limit/offset hit Workday's own pagination limits (limit<=20, offset<=10000). Workable is currently blocked by Cloudflare from this platform's edge and will throw a loud error naming the 429, not an empty result. Dover is NOT supported: its public board is a Cloudflare-Turnstile-gated SPA with no keyless jobs endpoint.

Input Schema

NameRequiredDescriptionDefault
atsYesWhich ATS to query.
filtersNoOptional post-fetch filters and Workday pagination controls.
board_tokenYesThe board identifier: Greenhouse/Lever/Ashby/SmartRecruiters/Teamtailor/Personio/Breezy/Pinpoint company slug or subdomain label; Recruitee/BambooHR subdomain label; Jobvite slug (path segment after jobs.jobvite.com/); Rippling slug (path segment after ats.rippling.com/); iCIMS full subdomain label before .icims.com (e.g. "careers-acme" — prefixes vary by customer); Workable account slug; Workday "<tenant>.wd<N>/<site>".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "ats": "greenhouse",
-    "board_token": "airbnb"
-  }
-]New value: +[
+  {
+    "ats": "greenhouse",
+    "board_token": "airbnb"
+  },
+  {
+    "ats": "teamtailor",
+    "board_token": "career"
+  },
+  {
+    "ats": "personio",
+    "board_token": "kertos"
+  },
+  {
+    "ats": "jobvite",
+    "board_token": "bagleybagelbites"
+  },
+  {
+    "ats": "breezy",
+    "board_token": "duolingo"
+  },
+  {
+    "ats": "pinpoint",
+    "board_token": "workwithus"
+  },
+  {
+    "ats": "rippling",
+    "board_token": "skillable-careers"
+  },
+  {
+    "ats": "icims",
+    "board_token": "careers-intrepidsolutions"
+  }
+]
    • changedInput schema / properties / ats / enum
      Previous value: -[
-  "greenhouse",
-  "lever",
-  "ashby",
-  "smartrecruiters",
-  "recruitee",
-  "bamboohr",
-  "workday",
-  "workable"
-]New value: +[
+  "greenhouse",
+  "lever",
+  "ashby",
+  "smartrecruiters",
+  "recruitee",
+  "bamboohr",
+  "workday",
+  "workable",
+  "teamtailor",
+  "personio",
+  "jobvite",
+  "breezy",
+  "pinpoint",
+  "rippling",
+  "icims"
+]
    • changedInput schema / properties / board_token / description
      Previous value: -"The board identifier: Greenhouse/Lever/Ashby/SmartRecruiters company slug or id; Recruitee/BambooHR subdomain label; Workable account slug; Workday \"<tenant>.wd<N>/<site>\"."New value: +"The board identifier: Greenhouse/Lever/Ashby/SmartRecruiters/Teamtailor/Personio/Breezy/Pinpoint company slug or subdomain label; Recruitee/BambooHR subdomain label; Jobvite slug (path segment after jobs.jobvite.com/); Rippling slug (path segment after ats.rippling.com/); iCIMS full subdomain label before .icims.com (e.g. \"careers-acme\" — prefixes vary by customer); Workable account slug; Workday \"<tenant>.wd<N>/<site>\"."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, openWorld, non-destructive), and the description adds substantial behavior beyond that: the found:false/board_not_found contract, per-ATS ambiguity (SmartRecruiters ambiguous:true, Pinpoint/iCIMS unconfirmed), Workday capped:true on pagination limits, Cloudflare-blocked Workable throwing a 429 error, and Dover outright unsupported.

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 core purpose and sibling routing are front-loaded in the first sentence, and the per-provider caveats are information-dense rather than padded. It is a long run-on paragraph, but nearly every clause carries operationally relevant content for a 15-provider tool.

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?

With no output schema, the description carries the return contract: it explains found:false/reason, the found:true/jobs:[] real-zero case, ambiguity markers, and capped:true. For a multi-provider fetch tool, this is complete enough for correct invocation and result interpretation.

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

Parameters3/5

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

Schema coverage is 100%, so the schema already documents ats, board_token, and every filter including Workday formats and Lever region. The description adds little parameter detail beyond what the schema states (the Workday token format appears in both), so baseline 3 is appropriate.

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 ('Fetch normalized job postings from a PUBLIC ATS board') and scopes the prerequisite ('you already have the ats + board_token'). It explicitly distinguishes itself from the sibling tools ats_detect and ats_company_jobs by naming when to use each.

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?

Explicitly routes the agent: use ats_detect or ats_company_jobs if you only have a domain. It also gives case-by-case guidance on interpreting zero-job vs unknown-board results per provider, and flags unsupported (Dover) and blocked (Workable) cases, which is genuine when/when-not guidance.

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

All Ats Boards 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