HireHeat

Company hiring signals

hiring_signals

Read-onlyIdempotent

Hiring SUMMARY for one company, read live from its public Greenhouse, Lever, Ashby, SmartRecruiters and Recruitee job board. Use this when you need to know whether a company is hiring, how fast and in which teams: sales triggers, account research, investor or competitor signals. Do not use it to read the postings themselves (use company_jobs). Input: company (website domain, website URL or job-board URL); optional keywords narrow the counts to matching job titles. Returns results[0] with found, the job board detected (ATS and URL), signals (open roles, roles posted in the last 7 and 30 days, hiring level, counts by function and seniority, top departments and locations, remote share, the 10 newest jobs), a one-line summary, checkedAt and cached. found=false means no supported public board was found (for example a Workday-only company). Limits: one company per call; answers cached for 1 hour; 20 free companies a day per IP without a key, more with a paid key in the x-api-key header. Read-only: nothing is stored or sent.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`company`	Yes	The company to check, one per call: its website domain, website URL, or a job-board URL (boards.greenhouse.io/acme, jobs.lever.co/acme, jobs.ashbyhq.com/acme)
`keywords`	No	Optional job-title keywords; only jobs whose title contains any of them are counted

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 10, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

changedInput schema / properties / company / description

Previous value: -"e.g. stripe.com or jobs.lever.co/acme"New value: +"The company to check, one per call: its website domain, website URL, or a job-board URL (boards.greenhouse.io/acme, jobs.lever.co/acme, jobs.ashbyhq.com/acme)"

addedInput schema / properties / company / examples
```
Added value: +[
+  "stripe.com"
+]
```

changedInput schema / properties / keywords / description

Previous value: -"optional title keywords"New value: +"Optional job-title keywords; only jobs whose title contains any of them are counted"

addedInput schema / properties / keywords / examples

Added value: +[
+  [
+    "engineer",
+    "sales"
+  ]
+]

First observedOct 1, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, openWorld, non-destructive), and the description adds substantial context beyond them: caching for 1 hour, a rate limit of 20 free companies/day per IP, one company per call, the meaning of found=false (e.g. Workday-only companies), and confirmation that nothing is stored or sent.

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 and the sibling exclusion, then usage, input, returns, limits. It is dense and runs long, with some overlap between the Input sentence and the schema, but nearly every clause carries useful information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description fully carries the burden of explaining return values: results[0] fields, found flag, ATS/URL, signals breakdown, summary, checkedAt and cached. Limits, inputs, and failure semantics are all covered, leaving nothing an agent needs to call it correctly.

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 description coverage is 100%, so both parameters are already documented. The description restates the same input semantics (domain/URL/job-board URL, optional keyword narrowing) without adding syntax or format detail beyond the schema, so the baseline 3 applies.

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+resource ('Hiring SUMMARY for one company') and enumerates the exact data sources (Greenhouse, Lever, Ashby, SmartRecruiters, Recruitee). It explicitly distinguishes itself from the sibling company_jobs, so an agent can route 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 Guidelines5/5

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

Gives explicit when-to-use contexts (sales triggers, account research, investor/competitor signals) and an explicit when-not ('Do not use it to read the postings themselves') with the named alternative company_jobs. Nothing is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All HireHeat tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?