Skip to main content
Glama

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.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ats": "greenhouse",
      "board_token": "airbnb"
    },
    "name": "ats_jobs"
  }
}

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. Changed1 schema field changed
    • changedInput schema / properties / board_token / description
      Previous 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>\"."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. 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>\"."
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/openWorld, yet the description still adds substantial behavior: the {found:false, reason:"board_not_found"} shape versus an empty jobs[], which ATSes can distinguish a real zero-job board, the SmartRecruiters ambiguous:true flag, the Workday capped:true pagination cap, and the loud 429 error for Workable. That is context an agent cannot get from 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the purpose and sibling routing, then a dense but largely waste-free caveat block. Each sentence carries a distinct edge case, though the per-ATS zero-job enumeration is long and would be easier to scan as structured notes rather than running prose.

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?

There is no output schema, and the description compensates by describing the response shape for both success and not-found paths, per-ATS ambiguity, and pagination caps. For a 15-value enum tool with nested filters, an agent has enough to call it and interpret results correctly.

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% and the schema already documents per-ATS board_token formats, the Workday '<tenant>.wd<N>/<site>' pattern, region applying to Lever only, and limit/offset being Workday-only. The description largely restates these, adding only the framing that the token must already be known.

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 — 'Fetch normalized job postings from a PUBLIC ATS board' — and immediately scopes the prerequisite ('you already have the ats + board_token'). It explicitly distinguishes itself from siblings ats_detect and ats_company_jobs, so an agent can route correctly without opening the 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?

Gives an explicit routing rule: use ats_detect or ats_company_jobs when you only have a domain. It also names unsupported/blocked cases (Dover not supported, Workable blocked by Cloudflare) so the agent knows when not to call it, which is exactly the exclusions bar for a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.