get_candidates

Read-only MCP tool that returns candidates for one sourcing using the same filters and ordering as the Kalent candidates table.

Input

Field	Type	Required	Description
`sourcingId`	string	yes	Sourcing id
`pageIndex`	number	no	Zero-based page index
`pageSize`	number	no	Page size (max 50)
`search`	string	no	Free-text search
`statusHandle`	string[]	no	Status filters
`location`	string[]	no	City filters
`jobTitle`	string[]	no	Job title filters
`currentCompany`	string[]	no	Company filters
`sortField`	string	no	One of `name`, `companyName`, `statusHandle`, `city`, `jobTitle`, `userRating`, `contacts`, `createdAt`, `history`
`sortOrder`	`asc` \| `desc`	no	Sort order

sortField: "history" is not a true activity sort: the page is selected by talent creation date (talent.createdAt, in the requested sortOrder), then the candidates of that page are re-ordered in memory by their latest outreach activity (with desc, candidates without any activity come first, then the most recent activity first). To find who replied, read replyStatus on each item rather than relying on this sort.

Response

Each item is { candidate, talent, lastActivityAt, lastActivityDirection, lastActivityChannel, lastActivityContent, replyStatus }.

Outreach activity

The latest outreach activity between the talent and the user who owns the API key, aggregated across every channel (LinkedIn, email, WhatsApp, SMS) and across legacy and dynamic sequences. This is the same scope as the candidates table this user sees in Kalent: messages and invitations sent by other members of the workspace are not taken into account. get_candidate returns the same fields with the same values.

Field	Type	Description
`lastActivityAt`	ISO-8601 string \| `null`	Date of the most recent outreach event: message sent, LinkedIn invitation sent or accepted, or reply received. `null` when the candidate was never contacted.
`lastActivityDirection`	`INBOUND` \| `OUTBOUND` \| `null`	`INBOUND` when the latest event comes from the talent (reply, accepted invitation), `OUTBOUND` when it comes from the API key owner (message or invitation sent). `null` when the candidate was never contacted.
`lastActivityChannel`	`LINKEDIN` \| `WHATSAPP` \| `EMAIL` \| `SMS` \| `null`	Channel of that latest event. `null` when the candidate was never contacted.
`lastActivityContent`	string \| `null`	Text of that latest event when it is a sent or received message. `null` when the candidate was never contacted, when the latest event is a LinkedIn invitation sent or accepted (Kalent does not store the invitation note), or when the message body is empty. Email subject is not included.
`replyStatus`	`REPLIED` \| `NO_REPLY` \| `NOT_CONTACTED`	`REPLIED` as soon as at least one reply was received on any channel, `NO_REPLY` when the talent was contacted without any reply, `NOT_CONTACTED` when no outreach happened.

replyStatus stays REPLIED even if a follow-up was sent after the talent replied (lastActivityDirection then becomes OUTBOUND). An accepted LinkedIn invitation counts as an inbound activity but not as a reply.

{
  "success": true,
  "data": {
    "candidates": [
      {
        "candidate": {
          "id": "candidate_123",
          "statusHandle": "CONTACTED",
          "createdAt": "2026-05-19T09:00:00.000Z",
          "sourcingId": "sourcing_123",
          "talentId": "talent_123"
        },
        "talent": {
          "id": "talent_123",
          "firstname": "Grace",
          "lastname": "Hopper",
          "jobTitle": "Software Engineer",
          "city": "Paris",
          "linkedinUrl": "https://www.linkedin.com/in/example"
        },
        "lastActivityAt": "2026-05-21T14:32:00.000Z",
        "lastActivityDirection": "INBOUND",
        "lastActivityChannel": "LINKEDIN",
        "lastActivityContent": "Yes, I am interested.",
        "replyStatus": "REPLIED"
      }
    ],
    "pagination": {
      "pageIndex": 0,
      "pageSize": 25,
      "total": 1,
      "hasNextPage": false
    }
  }
}

Getting Started

Embedded

Platform

Input

Response

Outreach activity

​Input

​Response

​Outreach activity

Input

Response

Outreach activity