MCP tool

watch_company

Subscribe to a company's hiring events on a registered webhook -- `webhook_endpoint_id` must belong to the same customer as the authenticated key. Meters one `watch` unit.

Read from com.reqbeat/hiring-signals v1.0.0 on July 30, 2026 at 12:01 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"
  }
}

Endpoint https://mcp.reqbeat.com/mcp, authenticated with the X-API-Key request header.

Input schema

{
  "properties": {
    "company_id": {
      "title": "Company Id",
      "type": "integer"
    },
    "event_types": {
      "items": {
        "type": "string"
      },
      "title": "Event Types",
      "type": "array"
    },
    "webhook_endpoint_id": {
      "title": "Webhook Endpoint Id",
      "type": "integer"
    },
    "idempotency_key": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null,
      "title": "Idempotency Key"
    },
    "plane_api_key": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null,
      "title": "Plane Api Key"
    }
  },
  "required": [
    "company_id",
    "event_types",
    "webhook_endpoint_id"
  ],
  "title": "watch_companyArguments",
  "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.