Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

jobs_workday_board

List a company's public Workday job board postings by tenant, datacenter, and site, with limit/offset paging and optional search.

Instructions

List a Workday tenant's job board. Lists a company's public Workday (CXS) postings, paged via limit/offset. tenant, datacenter (wd1/wd3/wd5/...), and site all come from the careers URL https://{tenant}.wd5.myworkdayjobs.com/{site}.

Input Schema

NameRequiredDescriptionDefault
siteYesWorkday career site
limitNoPage size, default 20, max 20
offsetNoPage offset, default 0
searchNoFree-text search
tenantYesWorkday tenant
datacenterYesWorkday datacenter shard (wd1, wd3, wd5, ...)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses that only public postings are returned and that results are paged via limit/offset, which is useful. It omits auth requirements, rate limits, and what a posting record contains, leaving notable gaps for a zero-annotation tool.

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 short sentences, with the core purpose front-loaded and the parameter-derivation hint following. No redundancy and no filler; every sentence adds information.

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 listing tool with no output schema or annotations, the description covers what it returns (public postings), how pages work, and how to source the required identifiers. It leaves return-field shape unspecified, which is acceptable since no output schema exists but would still help.

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 3 baseline applies, and the description adds real meaning beyond it by explaining the origin of the three required values (tenant/datacenter/site derived from https://{tenant}.wd5.myworkdayjobs.com/{site}) and the datacenter options. This goes beyond the schema's terse field descriptions.

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 specific verb and resource ('List a Workday tenant's job board') and immediately disambiguates scope with 'public Workday (CXS) postings'. An agent can distinguish this board-listing tool from the sibling detail tool jobs_workday_job, though it never names that sibling explicitly.

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 gives concrete usage context by telling the agent exactly where tenant, datacenter, and site come from (the careers URL pattern), which is the main practical hurdle to calling this tool. It does not, however, state when to prefer this over the individual-posting sibling or note any exclusions.

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