Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

jobs_ukg_board

List public job postings from a UKG Pro Recruiting tenant's job board. Page via limit/offset and search by keyword.

Instructions

List a UKG Pro Recruiting tenant's job board. Lists a UKG Pro Recruiting (formerly UltiPro) tenant's public opportunities, paged via limit/offset. tenant and board both come from the careers URL https://recruiting.ultipro.com/{tenant}/JobBoard/{board}. Each posting carries a brief description inline.

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": {
      "tenant": "<tenant>",
      "board": "<board>"
    },
    "name": "jobs_ukg_board"
  }
}

Input Schema

NameRequiredDescriptionDefault
boardYesUKG job-board UUID (careers URL)
limitNoPage size, default 25, max 50
offsetNoPage offset, default 0
searchNoFree-text keyword search
tenantYesUKG tenant code (careers URL)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

A3.6/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 full burden. It discloses that results are paged via limit/offset and that each posting carries a brief inline description, which is useful. It omits auth requirements, rate limits, and total-count/return structure, leaving real gaps for a no-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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action and efficiently packed. The opening sentence slightly restates the second (both say it lists the tenant's job board/opportunities), a small redundancy, but overall 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?

No output schema, but the description compensates by noting that postings include inline brief descriptions, and it covers pagination and parameter sourcing. Given 100% schema coverage and a simple list tool, it is largely complete, though auth behavior is unaddressed.

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, but the description adds meaning by giving the exact source URL pattern (https://recruiting.ultipro.com/{tenant}/JobBoard/{board}), clarifying where tenant and board come from and how they relate.

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 (List) and resource (a UKG Pro Recruiting tenant's public opportunities/job board), and clarifies the legacy UltiPro name. It does not distinguish itself from sibling board tools like jobs_greenhouse_board or jobs_icims_board, but the purpose is otherwise unambiguous.

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?

Usage is implied: this is the tool for UKG/UltiPro tenants, and tenant/board must come from the careers URL. However, there is no explicit when-to-use-vs-alternatives guidance and no exclusions relative to the many other jobs_* board tools.

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