Skip to main content
Glama

Workday jobs

workday_jobs
Read-onlyIdempotent

Fetch open job postings from any company's Workday career site, filtered by keywords, location, or posting date; optionally include full descriptions and pay ranges.

Instructions

List open jobs from any company's Workday career site (*.myworkdayjobs.com). Each item: title, requisition id, location, posted-on text, job URL, company; with include_description also job type, remote type, country, apply link, stated pay range and description text. Cost: $1.00 per 1,000 jobs on the user's Apify account; the default 20 jobs cost $0.02. Latency: usually 10-60 s (longer with descriptions).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "career_site_urls": "<career_site_urls>"
    },
    "name": "workday_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_itemsNoStop after this many jobs in total.
search_textNoOptional keywords, same as the site's search box.
career_site_urlsYesWorkday jobs pages, e.g. https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite
location_containsNoOptional. Keep jobs whose location contains this.
posted_within_daysNoOptional. Only jobs posted in the last N days.
include_descriptionNoLoad full description, pay range and apply link. Slower, same price.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare read-only, open-world, idempotent and non-destructive behavior, and the description adds genuinely new operational facts: the $1.00 per 1,000 jobs pricing with a concrete default-cost example ($0.02 for 20 jobs) and a 10-60 s latency range that grows with include_description. That is exactly the kind of billing and runtime context an agent needs before calling.

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?

Three sentences, each earning its place: scope first, return payload second, cost and latency last. No filler and no repetition of schema field definitions.

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?

Despite having an output schema, the definition still gives a compact return-value summary plus pricing and latency, which are not captured in any structured field. Nothing an agent needs to decide whether and how to call it is missing.

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 earns an extra point by explaining what include_description actually yields (job type, remote type, country, apply link, pay range, description text) and by tying the default max_items of 20 to the stated $0.02 cost.

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 ('List open jobs'), constrains the source domain ('any company's Workday career site (*.myworkdayjobs.com)'), and enumerates the returned fields. This is clearly distinguishable from generic siblings like ats_jobs or remote_jobs.

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?

The Workday-domain constraint implies when the tool applies, and the cost/latency notes help an agent plan a call. However, there is no explicit when-not-to-use statement or named alternative for non-Workday sites, so an agent must infer that ats_jobs or remote_jobs covers those cases.

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