MCP tool
get_role
One open role's detail, addressed by the `company_id` + `req_key` pair every `search_jobs` row already carries -- the follow-up call for a role you hold an identifier for, instead of re-pulling the whole company with `get_open_reqs`. Scoped exactly as `search_jobs` is: ATS-only and freshness-floored. The body adds `raw_title` (the posting's own title) and `boards`, the full deduped list of boards reporting this req. A role that does not exist, is closed, or has not reached the freshness floor is an explicit error, never an empty success -- and it is not billed. No key yet? On the hosted HTTP endpoint the first calls are free: send no `X-API-Key` header and the lookup runs on a shared demo credential, billed to nobody and marked as such, until a per-IP limit is reached.
Read from com.reqbeat/hiring-signals v1.1.2 on September 14, 2026 at 00:11 UTC · Refreshed every 3 hours
Connect
Reqbeat Hiring Signals is a remote MCP server over streamable HTTP. Paste this into your client's server config, replacing the placeholder with your own key:
{
"url": "https://mcp.reqbeat.com/mcp",
"headers": {
"X-API-Key": "YOUR_REQBEAT_API_KEY"
}
}
Or connect with no key at all. Same endpoint — leaving the
X-API-Key header off runs
the read tools in a rate-limited demo mode:
{
"url": "https://mcp.reqbeat.com/mcp"
}
Endpoint https://mcp.reqbeat.com/mcp, authenticated
with the X-API-Key request header.
Input schema
{
"properties": {
"company_id": {
"title": "Company Id",
"type": "integer"
},
"req_key": {
"title": "Req Key",
"type": "string"
},
"idempotency_key": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null,
"title": "Idempotency Key"
},
"plane_api_key": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null,
"description": "Deprecated: pass the key in the `X-API-Key` header, or omit the header for demo mode. Removed in 1.2.",
"title": "Plane Api Key"
}
},
"required": [
"company_id",
"req_key"
],
"title": "get_roleArguments",
"type": "object"
}
Calling it
No response is shown because this page never calls this tool. It either needs your own API key or changes state on the server, and publishing a doc page is not a reason to do either. The request above is real -- run it yourself.