Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

jobs_workday_job

Retrieve a single Workday job posting's full details—description, location, and req ID—from a board listing by passing tenant, datacenter, site, and external path.

Instructions

Get a single Workday job. Returns a single Workday posting's full detail (description, location, req id). path is the externalPath from a board listing. tenant/datacenter/site as in the board endpoint.

Input Schema

NameRequiredDescriptionDefault
pathYesJob externalPath from a board listing
siteYesWorkday career site
tenantYesWorkday tenant
datacenterYesWorkday datacenter shard

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It implies a read ('Get') and discloses the return payload (description, location, req id), which is useful since there is no output schema, but says nothing about auth, rate limits, or error behavior.

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 short, front-loaded sentences with essentially no waste. The opening pair ('Get a single Workday job. Returns a single Workday posting's full detail...') is slightly redundant but still tight.

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 low-complexity single-item read with full param coverage, the description is nearly sufficient: it describes the return content and the source of the required path. It could say more about failure modes when the path is stale, but nothing critical is missing.

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 coverage is 100%, so the schema already documents all four parameters (baseline 3). The description reinforces that tenant/datacenter/site come from the board endpoint, adding minor cross-reference context but no syntax or format detail beyond the schema.

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?

States a specific verb and resource ('Get a single Workday job') and clarifies the scope versus a board listing tool by noting the path comes 'from a board listing'. This lets an agent distinguish it from jobs_workday_board without opening the schema, though it never names the 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 Guidelines3/5

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

The guidance is implied rather than stated: 'path is the externalPath from a board listing' tells the agent it must first obtain a listing, but there is no explicit when-to-use/when-not or named alternative. Adequate but leaves the sequencing to inference.

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