MCP tool

write_outcome

Write back a conversion outcome for `company_id` -- the label-flywheel substrate. Appends to `outcome_labels` scoped to the caller's own customer. Plane session only: `outcome_labels` is plane-owned (Phase 1 dropped its one foreign key into the corpus) and this tool reads no corpus table.

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"
    },
    "outcome": {
      "title": "Outcome",
      "type": "string"
    },
    "observed_at": {
      "format": "date-time",
      "title": "Observed At",
      "type": "string"
    },
    "req_key": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null,
      "title": "Req Key"
    },
    "plane_api_key": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null,
      "title": "Plane Api Key"
    }
  },
  "required": [
    "company_id",
    "outcome",
    "observed_at"
  ],
  "title": "write_outcomeArguments",
  "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.