Skip to main content
Glama
zrk-scrapers-mcp

zrk-scrapers-mcp

by Zrk1212

Workday Jobs Scraper

scrape_workday_jobs

Scrape every job from Workday career sites, including listings past the 2,000-result cap, with title, location, date, salary, and full description.

Instructions

Scrape every job from any Workday career site (myworkdayjobs.com), including past Workday's 2,000-result cap. Pass Workday site URLs or company names. Returns title, location, posted date, parsed salary and full description. Priced per job returned. Runs the Apify actor zrk1212/workday-jobs-scraper on your Apify account.

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

Input Schema

NameRequiredDescriptionDefault
maxItemsNoMost result rows to return in this response (default 50). The run may produce more; page with get_run_results.
siteUrlsNoWorkday career site URLs, e.g. https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite
waitSecsNoSeconds to wait for the run to finish (default 120). If it is still running, use get_run_results later.
companiesNoCompany names to look up on Workday (use instead of or with siteUrls).
extraInputNoAny other input field of the Apify actor zrk1212/workday-jobs-scraper, passed through as-is. See https://apify.com/zrk1212/workday-jobs-scraper/input-schema
remoteOnlyNoOnly remote jobs.
searchTextNoWorkday search text, e.g. 'software engineer'.
maxChargeUsdNoHard spending cap for this run in USD (default 1). Apify stops charging when it is reached.
includeDetailsNoFetch full description and salary (default true).
locationKeywordsNoKeep jobs whose location contains any of these words.
postedWithinDaysNoOnly jobs posted in the last N days (0 = any).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare openWorldHint=true, idempotentHint=false and destructiveHint=false, so the description is not carrying the safety burden alone. It still adds genuinely useful behavior: it beats Workday's 2,000-result cap, bills per job returned, and executes the named Apify actor on the caller's account — information an agent cannot get from the annotations.

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 tight sentences, front-loaded with the resource and scope before mode of input, output and billing. Every sentence carries distinct information with no repetition of the title.

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 an 11-parameter tool with no output schema, the description supplies the return field list, the cost model and the actor identity, which covers most of what is needed. It omits only run-lifecycle behavior (the waitSecs/get_run_results paging handoff), which the parameter descriptions do cover.

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%, so every one of the 11 parameters is already documented, including maxItems, waitSecs and the extraInput passthrough. The description only restates the siteUrls/companies duality and never explains filtering parameters such as postedWithinDays, remoteOnly or maxChargeUsd, so it adds little beyond the schema and the baseline 3 applies.

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 every job") and narrowly scopes it to Workday career sites at myworkdayjobs.com, which cleanly separates it from the generic sibling scrape_ats_jobs. The cap-bypass claim and the returned field list make the tool's identity unmistakable.

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

Usage Guidelines3/5

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

"Pass Workday site URLs or company names" gives concrete invocation guidance, but there is no statement of when to choose this over scrape_ats_jobs or any exclusion conditions. Usage is implied by the domain restriction rather than explicitly argued.

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