Skip to main content
Glama
Apify Public Data & Leads

Apify Public Data & Leads

Company Job Postings (Greenhouse, Lever, Ashby)

company_job_postings
Read-only

Collect open job postings from Greenhouse, Lever, and Ashby career boards in one call, returning company, title, location, department, posting date, salary, and apply URL as structured rows.

Instructions

Collect live job postings straight from company career boards in one call: one row per open job with company, ATS, job id, title, location, department, employment type, workplace type, posting date, apply URL, salary text when the board publishes it, and the description as plain text (optional). Give it board tokens or career-page URLs for Greenhouse ('stripe'), Lever ('leverdemo') or Ashby ('ramp'). A call must name at least one board.

Behavioral Transparency:

  • Execution: Network call executed synchronously in the cloud via Apify Actor 'captainhandsome/job-postings-scraper'.

  • Side Effects: Reads each platform's public job-board JSON endpoint (the same data the company's own careers page loads) and creates a billed Actor run and dataset on your Apify account. No login, no API key, no cookies, no browser.

  • Authentication: Requires APIFY_TOKEN environment variable.

  • Latency & Limits: Typically 2-20 seconds. $0.003 per job row plus $0.005 per run. This tool sends at most 3 boards per platform and at most 10 jobs per board, so one call bills at most 90 rows; raise max_jobs_per_company only if you want larger boards. (The Actor itself accepts more boards and jobs when called directly on Apify.)

Usage Guidelines:

  • When to use: Use for hiring-signal lead lists (which accounts are opening which roles), job-market research across a handful of companies, recruiting and competitor intel, or filling a job board or newsletter with fresh roles from companies you choose.

  • When NOT to use: Do not use for closed or archived postings (boards expose currently open jobs only), for LinkedIn, Indeed or ZipRecruiter aggregator data, or for Workable boards (its public endpoint rate-limits datacenter IPs and is deliberately not supported).

  • Named alternatives: the other tools in this package cover Shopify catalogs, app stores, podcasts and newsletters, not job boards.

Honest limits: only Greenhouse, Lever and Ashby are supported; a private or removed board returns nothing for that company and the run continues with the rest; boards that publish no posting date or salary leave those fields null rather than inventing them; descriptions are trimmed to 4,000 characters. Board lists are sent explicitly on every call, so an omitted platform is skipped, never replaced by a hidden default search.

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": "company_job_postings"
  }
}

Input Schema

NameRequiredDescriptionDefault
ashbyNoUp to 3 Ashby organisation names or URLs, e.g. 'ramp' or 'https://jobs.ashbyhq.com/ramp'. Leave out to skip Ashby.
leverNoUp to 3 Lever board tokens or URLs, e.g. 'leverdemo' or 'https://jobs.lever.co/leverdemo'. Leave out to skip Lever.
queryNoOptional keyword filter applied to job title and description, e.g. 'engineer'. Leave empty for all jobs.
greenhouseNoUp to 3 Greenhouse board tokens or URLs, e.g. 'stripe' or 'https://boards.greenhouse.io/stripe'. Leave out to skip Greenhouse.
posted_within_daysNoKeep only jobs posted in the last N days. 0 means no date filter; boards that expose no date are kept.
include_descriptionNoWhen true, each row carries the posting description as plain text trimmed to 4,000 characters. Set false for a smaller, faster dataset.
max_jobs_per_companyNoUpper limit of postings returned per board (hard maximum 10). Each row is a billed result.

Output Schema

NameRequiredDescriptionDefault
runNo
errorNo
statusYes
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

A4.5/5.0
Behavior4/5

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

Goes well beyond the annotations: it discloses the Actor name, synchronous cloud execution, the fact that a billed run and dataset are created on the Apify account, the required APIFY_TOKEN, expected latency, per-row and per-run pricing, and hard caps of 3 boards per platform and 10 jobs per board. It also states honest data limits (null dates/salary, 4,000-char description trim) and that an unsupported/private board silently returns nothing.

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?

Despite its length, every block is a labeled, front-loaded fact set (behavior, usage, limits) with no filler sentences; the purpose lands in the first sentence before any caveats. Length is proportionate to a 7-parameter, multi-platform, billed network 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 an output schema present the field-by-field return list is redundant but harmless, and annotations already cover safety; the description still supplies the auth requirement, cost model, latency, platform coverage boundaries, and data-quality caveats an agent needs to call this correctly and interpret empty results as 'board not found' rather than an error.

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 already 100%, but the description adds meaning the schema cannot express: a call 'must name at least one board' (notably, the schema marks no parameters required), and the billing consequence of the per-board/per-job caps, with guidance that max_jobs_per_company should be raised only deliberately. It does not add format detail for query or posted_within_days beyond 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?

The opening sentence gives a specific verb (collect) plus resource (live job postings from company career boards), enumerates the returned fields, and names the three supported ATS platforms with example board tokens. An agent can distinguish this from generic search tools 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 Guidelines4/5

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

It provides explicit when-to-use (hiring-signal lead lists, job-market research, recruiting intel) and when-not-to-use (closed postings, LinkedIn/Indeed/ZipRecruiter aggregators, Workable). The 'named alternatives' sentence, however, claims the rest of the package covers only Shopify apps/podcasts/newsletters and 'not job boards', which is misleading given job-board-oriented siblings, so routing to the correct alternative is only partially resolved.

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