Hiring Signals

kadi_bence/workday-jobs-scraper

kadi_bence--workday-jobs-scraper

Destructive

This tool calls the Actor "kadi_bence/workday-jobs-scraper" and retrieves its output results. Actor description: Get open jobs of any company by name: NVIDIA, Salesforce, Intel (Workday) and Stripe, Ramp (Greenhouse, Lever, Ashby, Workable, Personio) in one run, system auto-detected. Filters: title, country, date. Returns per job: title, team, location, salary, date, URL. Default: 20/company. $0.90/1K.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`waitSecs`	No	Max seconds (0–45, default 30) to cap the wait for the Actor run to reach terminal state. For long-running Actors the response returns at the cap with the current run status; follow `nextStep` to poll via get-actor-run. Set to 0 to fire-and-forget.
`companies`	No	Easiest option: type company names or domains, one per line, e.g. NVIDIA, Salesforce, intel.com. The Actor finds their Workday career site(s) automatically; the RUN_SUMMARY record lists the boards it found. A domain is more precise than a common word (target.com instead of Target). Companies not on Workday (e.g. Stripe) are looked up on Greenhouse, Lever, Ashby, Workable, Recruitee and Personio automatically. If a company is still not found, paste its career site URL below. Example values: ["NVIDIA"]
`countries`	No	Keep only jobs in these countries: names or ISO codes, e.g. US, Germany, GB. Jobs with several locations are kept if ANY location matches. Uses the career site's own country filter when it has one (faster). Other words (e.g. California) are matched as location text. Filtered-out jobs are not charged.
`startUrls`	No	Or paste Workday career site URLs, e.g. https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite. A URL with filters applied on the career site (location, category, search) keeps those filters. Single job URLs work too (the whole board is scraped).
`careerSites`	No	Large companies often run several Workday boards (main, students, subsidiaries). 'All' scrapes every public board; 'Main only' picks the primary external board. Example values: "all"	all
`monitorName`	No	Use different names to keep separate 'already seen' lists for different schedules with the same URLs. Example values: "default"	default
`onlyNewJobs`	No	Remember which jobs were already returned and output only NEW postings on the next runs. Ideal for scheduled runs (daily alerts). The first run outputs everything and stores a baseline. You only pay for new jobs.
`titleExcludes`	No	Drop jobs whose title contains ANY of these words, e.g. intern, senior, manager. Not case-sensitive ('intern' also drops 'International'; use 'internship' to be precise). Filtered-out jobs are not charged.
`titleIncludes`	No	Keep only jobs whose title contains ANY of these words, e.g. engineer, data scientist. Not case-sensitive. Leave empty for all titles. Filtered-out jobs are not saved and not charged.
`includeDetails`	No	Fetch each job's detail page: description, exact posted date, all locations, country, salary. Turn off for a faster, cheaper title/location-only list. Example values: true
`maxConcurrency`	No	Parallel requests to the career site. Keep it low to be polite; 4 is fast enough for most boards. Example values: 4
`maxJobsPerSite`	No	Stop after this many jobs per career site. 0 = no limit (all jobs, even boards with 10,000+ postings). The Console prefill is 50 for a quick test run. The default without input (API, MCP and AI-agent calls) is 20. Example values: 50
`searchKeywords`	No	Optional full-text search, exactly like the search box on the career site (e.g. "data engineer"). Leave empty for all jobs.
`postedWithinDays`	No	Only return jobs posted in the last N days (e.g. 7). Leave empty for any date.
`stripContactInfo`	No	Recommended (GDPR). Some postings include a recruiter's personal contact details; this removes them. Example values: true
`descriptionFormat`	No	How to output the job description. Example values: "text"	text
`proxyConfiguration`	No	Usually not needed: Workday career sites are public. Enable Apify Proxy only if you see many 403/429 errors. Example values: {"useApifyProxy":false}
`otherSystemsFallback`	No	When a company name has no Workday career site, look for its Greenhouse, Lever, Ashby, Workable, Recruitee or Personio job board instead (e.g. Stripe, Ramp, Hugging Face), so one run covers big employers and startups. Same output fields; the 'ats' field shows the source. Example values: true

Output Schema

TableJSON Schema

Name	Required	Description
`tip`	No	Advisory guidance RAG Web Browser wrote to its key-value store under the reserved "TIP" key
`runId`	Yes	Actor run ID
`stats`	No	Run statistics
`status`	Yes	Run status: READY \| RUNNING \| TIMING-OUT \| TIMED-OUT \| ABORTING \| ABORTED \| SUCCEEDED \| FAILED
`actorId`	Yes	Stable Apify Actor ID from the run record
`summary`	Yes	Past-tense summary of the run state
`exitCode`	No	Actor process exit code; populated for terminal states (especially FAILED)
`nextStep`	Yes	One primary follow-up action with identifiers interpolated
`storages`	Yes	Dataset and key-value store metadata, keyed by alias. "default" is always the primary entry.
`actorName`	No	"username/actor-name"
`startedAt`	No	ISO timestamp when the run started
`finishedAt`	No	ISO timestamp when the run finished (terminal states only)
`statusMessage`	No	Pass-through from Apify run.statusMessage
`apifyConsoleUrl`	No	Personalized Apify Console link to the run; present only for Console sessions

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 5, 2026

changedInput schema / properties / companies / description

Previous value: -"Easiest option: type company names or domains, one per line, e.g. NVIDIA, Salesforce, intel.com. The Actor finds their Workday career site(s) automatically; the RUN_SUMMARY record lists the boards it found. A domain is more precise than a common word (target.com instead of Target). If a company is not found, it may use another applicant system, or you can paste its career site URL below.\nExample values: [\"NVIDIA\"]"New value: +"Easiest option: type company names or domains, one per line, e.g. NVIDIA, Salesforce, intel.com. The Actor finds their Workday career site(s) automatically; the RUN_SUMMARY record lists the boards it found. A domain is more precise than a common word (target.com instead of Target). Companies not on Workday (e.g. Stripe) are looked up on Greenhouse, Lever, Ashby, Workable, Recruitee and Personio automatically. If a company is still not found, paste its career site URL below.\nExample values: [\"NVIDIA\"]"

changedInput schema / properties / companies / items / description

Previous value: -"Easiest option: type company names or domains, one per line, e.g. NVIDIA, Salesforce, intel.com. The Actor finds their Workday career site(s) automatically; the RUN_SUMMARY record lists the boards it found. A domain is more precise than a common word (target.com instead of Target). If a company is not found, it may use another applicant system, or you can paste its career site URL below."New value: +"Easiest option: type company names or domains, one per line, e.g. NVIDIA, Salesforce, intel.com. The Actor finds their Workday career site(s) automatically; the RUN_SUMMARY record lists the boards it found. A domain is more precise than a common word (target.com instead of Target). Companies not on Workday (e.g. Stripe) are looked up on Greenhouse, Lever, Ashby, Workable, Recruitee and Personio automatically. If a company is still not found, paste its career site URL below."

addedInput schema / properties / otherSystemsFallback

Added value: +{
+  "default": true,
+  "description": "When a company name has no Workday career site, look for its Greenhouse, Lever, Ashby, Workable, Recruitee or Personio job board instead (e.g. Stripe, Ramp, Hugging Face), so one run covers big employers and startups. Same output fields; the 'ats' field shows the source.\nExample values: true",
+  "examples": [
+    true
+  ],
+  "title": "Also find companies that are not on Workday",
+  "type": "boolean"
+}

First observedOct 5, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations declare readOnlyHint=false, destructiveHint=true and openWorldHint=true, so the safety profile is largely covered. The description adds useful economics ('Default: 20/company', '$0.90/1K') but does not disclose that invoking it kicks off a billable, possibly long-running Actor run whose result may return at a waitSecs cap rather than terminal state — that nuance lives only in the schema.

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?

Two sentences, front-loaded, with the generic 'This tool calls the Actor ... and retrieves its output results' boilerplate leading into a dense, information-rich actor summary. Little waste, though the opening boilerplate is low-value.

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?

An output schema exists, so return values need not be explained, and 100% schema coverage plus explicit annotations mean the structured fields carry most of the detail. The description supplies purpose, cost, and source coverage adequately; the main missing piece is routing guidance against the near-identical ats-jobs-scraper sibling.

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 description coverage is 100% and the schema itself is unusually rich (per-param examples, defaults, prefill notes), so it carries the parameter burden. The description restates a few filters (title, country, date) and the 20/company default but adds no syntax or semantics beyond what the schema already documents.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a concrete verb+resource ('calls the Actor ... retrieves its output results') and then enumerates what the scraper returns (title, team, location, salary, date, URL) and its sources (Workday plus Greenhouse/Lever/Ashby/Workable/Personio). It does not, however, distinguish itself from the sibling kadi_bence--ats-jobs-scraper, whose scope clearly overlaps with the 'other ATS systems' clause here.

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

Usage Guidelines2/5

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

It conveys context (default 20/company, system auto-detected, $0.90/1K) but never states when to use this tool versus the ats-jobs-scraper sibling or the polling siblings (get-actor-run). No when-not or alternative-selection guidance is present.

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

All Hiring Signals tools Inspect

Try in Browser

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

Glama MCP Gateway

Add one secure layer between your agents and this server.