Skip to main content
Glama
zrk-scrapers-mcp

zrk-scrapers-mcp

by Zrk1212

ATS Jobs Scraper (Greenhouse, Lever, Ashby +6)

scrape_ats_jobs

Scrapes open jobs from company careers pages across Greenhouse, Lever, Ashby and other ATS platforms, auto-detecting the ATS. Returns job titles, locations, remote flags, salaries and descriptions.

Instructions

Scrape open jobs from company careers pages on Greenhouse, Lever, Ashby, SmartRecruiters, Workable, Recruitee, Personio, Teamtailor and Rippling. Pass careers URLs or plain company names; the ATS is auto-detected. Returns title, location, remote flag, department, parsed salary, posted date and description. Priced per job returned. Runs the Apify actor zrk1212/ats-jobs-monitor on your Apify account.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "companies": "<companies>"
    },
    "name": "scrape_ats_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxItemsNoMost result rows to return in this response (default 50). The run may produce more; page with get_run_results.
waitSecsNoSeconds to wait for the run to finish (default 120). If it is still running, use get_run_results later.
companiesYesCareers page URLs (e.g. https://jobs.ashbyhq.com/linear) or company names (e.g. 'Discord').
extraInputNoAny other input field of the Apify actor zrk1212/ats-jobs-monitor, passed through as-is. See https://apify.com/zrk1212/ats-jobs-monitor/input-schema
remoteOnlyNoOnly remote jobs.
maxChargeUsdNoHard spending cap for this run in USD (default 1). Apify stops charging when it is reached.
titleKeywordsNoKeep jobs whose title contains any of these words.
locationKeywordsNoKeep jobs whose location contains any of these words.
postedWithinDaysNoOnly jobs posted in the last N days (0 = any).
maxJobsPerCompanyNoCap per company (default 30).
includeDescriptionNoInclude the plain-text job description (default true).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare it is a non-read-only, open-world, non-idempotent but non-destructive operation. The description adds meaningful economics the annotations do not: billing is per job returned and the run executes on the caller's own Apify account. However, it says nothing about run duration or what happens when the wait budget expires, which for a long-running scrape is the main behavioral risk.

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?

Four dense sentences with zero filler; the purpose and platform list come first, then input forms, then outputs, then cost/execution model. Each sentence carries distinct information an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 11 parameters, a nested extraInput passthrough and no output schema, the description does well by naming the returned fields and the pricing model. It leaves the async run/polling lifecycle entirely to the schema text on waitSecs and get_run_results, which is a minor gap given the sibling tool exists for that purpose.

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, and the description earns above that by clarifying the most ambiguous parameter: 'companies' accepts either careers URLs or plain names with ATS auto-detection. It does not explain how maxItems interacts with maxJobsPerCompany or the per-job pricing, which would have closed the loop.

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 ('Scrape open jobs from company careers pages') and enumerates the nine supported ATS platforms, which immediately distinguishes it from the Workday-specific sibling. The return fields are named as well, so an agent knows exactly what it is getting.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains the accepted input forms ('Pass careers URLs or plain company names; the ATS is auto-detected'), which is real usage guidance for constructing a call. It stops short of stating when to prefer this over scrape_workday_jobs or other sibling scrapers, so an explicit alternative routing is missing.

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