Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

jobs_hiring_signals

Aggregate a company's ATS board into a hiring snapshot: open roles, department/location/title breakdowns, remote share, and new roles in 7/30 days to gauge growth.

Instructions

Aggregate hiring signals for a company's board. Aggregates a company's ATS board into a hiring snapshot: total open roles, breakdowns by department/location/title, remote share, and how many roles are new in the last 7/30 days — a leading indicator of company growth. Supply provider plus that provider's slug params (token / company / org / tenant+datacenter+site / domain). Breakdowns are computed over the fetched postings.

Input Schema

NameRequiredDescriptionDefault
orgNoashby org slug
hostNooracle cloud host (*.oraclecloud.com)
siteNoworkday / oracle career site
boardNoukg job-board UUID
tokenNogreenhouse board token
domainNoicims careers domain / eightfold organization domain
tenantNoworkday / eightfold tenant
companyNolever / smartrecruiters / workable / recruitee / rippling / personio / teamtailor / gem / pinpoint company slug
providerYesATS provider
datacenterNoworkday datacenter shard

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / provider / enum
      Added value: +[
+  "greenhouse",
+  "lever",
+  "ashby",
+  "workday",
+  "smartrecruiters",
+  "workable",
+  "recruitee",
+  "rippling",
+  "personio",
+  "teamtailor",
+  "oracle",
+  "ukg",
+  "icims",
+  "eightfold",
+  "gem",
+  "pinpoint"
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / company / description
      Previous value: -"lever / smartrecruiters / workable / recruitee / rippling / personio / teamtailor company slug"New value: +"lever / smartrecruiters / workable / recruitee / rippling / personio / teamtailor / gem / pinpoint company slug"
  3. Changed6 schema fields changedv1.6.0
    • addedInput schema / properties / board
      Added value: +{
+  "description": "ukg job-board UUID",
+  "type": "string"
+}
    • changedInput schema / properties / company / description
      Previous value: -"lever / smartrecruiters company slug"New value: +"lever / smartrecruiters / workable / recruitee / rippling / personio / teamtailor company slug"
    • addedInput schema / properties / domain
      Added value: +{
+  "description": "icims careers domain / eightfold organization domain",
+  "type": "string"
+}
    • addedInput schema / properties / host
      Added value: +{
+  "description": "oracle cloud host (*.oraclecloud.com)",
+  "type": "string"
+}
    • changedInput schema / properties / site / description
      Previous value: -"workday career site"New value: +"workday / oracle career site"
    • changedInput schema / properties / tenant / description
      Previous value: -"workday tenant"New value: +"workday / eightfold tenant"
  4. Addedv1.5.0

TDQS

A3.6/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, and it does disclose what the response aggregates and that 'breakdowns are computed over the fetched postings.' However it omits behavioral traits an agent needs: whether data is live or cached, error handling for a mismatched provider/slug, and rate limits.

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 sentences, front-loaded with purpose, then outputs, then parameter construction. Mostly efficient, though 'Aggregate hiring signals... Aggregates a company's ATS board' is a mildly redundant opening that repeats the verb.

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?

There is no output schema, so the description correctly spells out the returned snapshot fields, and it covers the required provider plus slug construction for a complex 10-parameter tool. It stops short of covering data freshness and failure modes, but is otherwise sufficient to call the tool correctly.

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 a routing rule by grouping which slug parameter pairs with which provider ('token / company / org / tenant+datacenter+site / domain') and signals that Workday needs a multi-param combo. This helps an agent pick the right slug field for a 16-provider enum, though much of the pairing is already implied by the schema 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 ('Aggregate hiring signals for a company's ATS board') and enumerates the exact outputs (total open roles, breakdowns by department/location/title, remote share, new roles in 7/30 days). This clearly separates it from the raw-listing siblings like jobs_greenhouse_board or jobs_workday_board, though it never names an alternative 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?

It hints at a use case ('a leading indicator of company growth') and tells the agent how to build the call ('Supply provider plus that provider's slug params'), but gives no explicit when-to-use vs when-not guidance and never contrasts itself with the many sibling board/posting tools that return raw jobs.

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