Skip to main content
Glama
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: total open roles, department/location/title breakdowns, remote share, and new roles in last 7/30 days—a leading indicator of company 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. Credential-free public ATS JSON.

Input Schema

TableJSON 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

A4.1/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It usefully discloses that the tool is credential-free, works on public ATS JSON, and computes breakdowns over fetched postings. However, it does not mention error behavior, rate limits, or what happens when required provider-specific params are missing, leaving notable gaps.

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?

The description is compact and information-dense, with the core purpose front-loaded. There is slight redundancy between 'Aggregate hiring signals' and 'Aggregates a company's ATS board into a hiring snapshot,' but overall every sentence contributes meaningful detail.

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 tool with 10 parameters, 16 providers, and no output schema, the description covers the essential ground: what the snapshot contains, how breakdowns are computed, and which parameter groups to supply. It stops short of giving exact provider-to-parameter mappings or edge-case behavior, but it is sufficiently complete for an agent to invoke it correctly in most cases.

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 schema already documents each parameter individually. The description adds value beyond the schema by grouping provider-specific slug params (token / company / org / tenant+datacenter+site / domain), helping the agent understand which parameter combinations apply to which provider.

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?

The description uses a specific verb ('Aggregate') and resource ('a company's ATS board') and clearly distinguishes itself from sibling board-fetching tools by describing an aggregated hiring snapshot rather than raw postings. It enumerates concrete outputs (total open roles, breakdowns, remote share, new roles), leaving no ambiguity about what the tool does.

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?

The description gives clear context on when to use this tool: when a hiring snapshot or leading indicator of company growth is needed. It does not explicitly name alternatives or state when not to use it, but the aggregation-focused framing implicitly separates it from raw board-fetching siblings.

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