Skip to main content
Glama
Job Posting Liveness Checker MCP Server

Job Posting Liveness Checker MCP Server

Check if job postings are still open, with posted date and age

check_job_posting_liveness
Read-onlyIdempotent

Check job posting URLs from Greenhouse, Lever, Ashby, Workday, or SmartRecruiters to see if each role is live or closed, with title, company, location, posted date, age, and last-seen-live time.

Instructions

Give job posting URLs from Greenhouse, Lever, Ashby, Workday, or SmartRecruiters. Returns one row per URL: live or closed, job title, company, location, posted date, age in days, and when a run on your account last saw it live. Reads each ATS's own public job API. Pay per event on Apify: 0.003 USD per posting checked; unsupported URLs are free.

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

Input Schema

NameRequiredDescriptionDefault
job_urlsNoPosting URLs from Greenhouse (boards.greenhouse.io, job-boards.greenhouse.io, or a company site with ?gh_jid=), Lever (jobs.lever.co), Ashby (jobs.ashbyhq.com), Workday (*.myworkdayjobs.com), or SmartRecruiters (jobs.smartrecruiters.com). Up to 5,000 per run. From Clay, put the column inside a one item list.
max_charge_usdNoOptional. The run stops before a charge that would pass this amount. Rows already checked are returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered structurally. The description adds real value beyond that: the pricing model (0.003 USD per posting, free for unsupported URLs), the retrieval method (each ATS's own public job API), and the per-URL row granularity. It doesn't discuss rate limits Or error behavior per failed URL, which keeps it at 4.

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?

Three compact sentences: input contract, output shape, then pricing/mechanics. Front-loaded and free of filler, though the pricing sentence packs cost and API-source details together in a way that's slightly dense.

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?

For a two-parameter read-only tool with 100% schema coverage and no output schema, the description covers what an agent needs: accepted URL formats, result columns, batching limits (in schema), and cost behavior. Return format detail is partly deferred to the enumeration in the description rather than an output schema, which is adequate but not exhaustive.

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; the description adds a bit by tying the charge limit to a stop-before-charge semantic ('rows already checked are returned') and by stating the per-posting price so max_charge_usd has a concrete denominator. The schema itself carries the URL pattern list.

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 description opens with a specific instruction and resource — job posting URLs from named ATS platforms — and states exactly what comes back: live/closed status, title, company, location, posted date, age, and last-seen-live time. The title reinforces this, and an agent can distinguish this from search- or fetch-style tools without ambiguity.

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 states the input form (posting URLs, with supported ATS domains enumerated) and mentions unsupported URLs are free, which hints at a graceful handling path. There's no sibling tool to route to and no explicit 'don't use for X' exclusion, keeping it just shy of a 5.

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

Deploy Server

Other Tools