Skip to main content
Glama
ginugokz

ATS Jobs Gateway: Workday, Greenhouse, Lever & Ashby

by ginugokz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
APIFY_TOKENNoApify API token from console.apify.com/settings/integrations. Needed only when a tool is called; tool calls run the hosted Actor and are billed pay-per-event on Apify.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
scrape_ats_jobsA

Extract open job postings from Workday, Greenhouse, Lever and Ashby career sites.

Args:
    urls: Full career-site URLs; the ATS is detected from the host
        (myworkdayjobs.com, myworkdaysite.com, greenhouse.io, lever.co,
        ashbyhq.com). Bare board names such as "stripe" are rejected. Examples:
        "https://nvidia.wd5.myworkdayjobs.com/en-US/NVIDIAExternalCareerSite",
        "https://boards.greenhouse.io/stripe", "https://jobs.lever.co/spotify",
        "https://jobs.ashbyhq.com/ramp".
    only_deltas: Return only jobs that are ADDED, UPDATED or REMOVED since the
        previous run (change tracking is stored in your Apify account).
    max_jobs: Maximum jobs per company, 1-500.
    include_details: Include full job descriptions and salary extraction.

Returns a dict with ``count`` and ``jobs`` (title, url, locations, posted_date,
employment_type, remote_type, compensation_raw, description_html, delta_status,
source_system: workday_cxs | greenhouse | lever | ashby, ...).
Billing: pay-per-event on Apify; see the Actor's Pricing tab.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
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

TDQS

A4.4/5.0

Scored across 1 tool

Disambiguation5/5

There is only one tool, so there is no possibility of confusing it with another. Its purpose (extracting ATS job postings) is stated clearly and unambiguously.

Naming Consistency5/5

The single tool name 'scrape_ats_jobs' follows a clean snake_case verb_noun convention. With one tool there is trivially no naming inconsistency across the set.

Tool Count3/5

A single tool is borderline thin for a server claiming to gateway four distinct ATS platforms, and it front-loads all behavior into parameter flags. It is not trivial given the rich parameters, but the surface feels under-decomposed.

Completeness4/5

For a read-only extraction domain, the tool covers the core workflow: multi-ATS scraping, delta change tracking, job limits, and detailed descriptions/salary. Minor gaps remain, such as no ATS discovery/validation helper or a standalone single-job lookup, which agents must work around.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources