Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

jobs_oracle_board

List public job requisitions from an Oracle Recruiting Cloud tenant's careers site using paging and keyword search.

Instructions

List an Oracle Recruiting (ORC) tenant's job board. Lists an Oracle Recruiting Cloud tenant's public requisitions, paged via limit/offset. host and site both come from the careers URL https://{host}/hcmUI/CandidateExperience/en/sites/{site}/ (host must be an *.oraclecloud.com hostname; site looks like CX_1). The listing carries a short description; use the single-job endpoint for full detail.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostYesOracle Cloud host (careers URL, *.oraclecloud.com)
siteYesOracle career site number
limitNoPage size, default 25, max 50
offsetNoPage offset, default 0
searchNoFree-text keyword search

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does meaningful work: it discloses pagination via limit/offset, the format constraints (host must be *.oraclecloud.com, site looks like CX_1), and that listing entries are abbreviated. It omits auth/permission or rate-limit behavior, which keeps it from a 5.

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 purpose, then supporting format and routing detail. The two opening sentences ('List an Oracle Recruiting (ORC) tenant's job board' vs 'Lists an Oracle Recruiting Cloud tenant's public requisitions') are near-duplicative, a small amount of waste.

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 5-parameter, no-output-schema, no-annotation tool, the description covers purpose, pagination, format constraints, and routing to the detail sibling. It leaves auth behavior unstated, a minor gap for an otherwise self-contained definition.

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 genuine meaning: it explains that host and site are both derived from the careers URL pattern and imposes a host suffix constraint and site format example beyond the terse schema text.

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 an Oracle Recruiting (ORC) tenant's job board' / 'public requisitions') and distinguishes itself from the single-job sibling by pointing to it for full detail. An agent can tell this apart from jobs_oracle_job without opening either schema.

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?

Provides a clear routing rule: use this for the board listing, and use the single-job endpoint when full detail is needed, since the listing carries only a short description. It stops short of naming when-not to use it (e.g. versus other ATS board tools), so it is clear context rather than full 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