Request an intro
requestIntroAsk Clera to introduce a candidate to your company for one of your open roles. Can start candidate outreach and submit an application to a connected hiring system. Target either a candidate from searchCandidates (talentId, with jobId or the interactive role picker) or an entry from listPendingIntroRequests / listRecommendedCandidates (its opportunityId, with talentName and roleName copied verbatim from that entry). When the user has not named a role, call this WITHOUT jobId and they pick the role in an interactive form; submitting it sends the request. reason carries only what the user said; your own view of the candidate goes in assistantNote. Fit flags are never a gate: a conflict flag is something to tell the user, not a reason to withhold the call. The response carries the flags as they stand at request time; pass them on. Re-requesting the same candidate for the same role sends nothing new and is safe. Refer to candidates and roles by name; the user never sees ids.
Clera privately records this tool's inputs and results for usage tracking and support.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "requestIntro"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| jobId | No | The open role to request the intro for. Resolve the id yourself with the job tool's list command when the user already named a role. When the role is not settled, omit it and CALL THE TOOL ANYWAY; the user gets an interactive role picker. Never list roles in chat and never ask the user for an id. | |
| orgId | No | Organization to act as. Only needed when you belong to more than one organization. | |
| reason | No | What the user said about why they want this candidate, in their own words, quoted or lightly trimmed and in their voice, e.g. 'The HPC master's is interesting for our infra work.' No lead-in such as 'the hiring manager said' or 'per the user'. Never fill it from the profile, fit flags, fit headline or your own reading of the candidate; that belongs in assistantNote. When the user gave no reason, ask once if the conversation allows it, otherwise leave it out. Stored on the opportunity as the company's reason. | |
| category | No | Only when the user's own words name it: strong_stack_match (tech stack fits) | great_trajectory (career growth) | domain_fit (industry experience aligns) | founder_energy (startup mindset). Leave it out otherwise. | |
| roleName | No | When acting on a listed opportunity, the role name copied verbatim from the same row. Checked against the record; a mismatch is refused. | |
| talentId | No | The candidate's id, exactly as returned by searchCandidates. Pair it with jobId. | |
| talentName | No | When acting on a listed opportunity, the talent's name copied verbatim from that row. Checked against the record; a mismatch is refused. | |
| assistantNote | No | Your own remarks for Clera, kept apart from the user's reason and never shown as the company's view: what the profile or fit flags say, a profile fact that contradicts what the user said, something to check. Leave it out when you have nothing to add. | |
| opportunityId | No | Alternative target: the opportunity id from a listPendingIntroRequests or listRecommendedCandidates row. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| flags | Yes | Fit flags for this candidate against the role, computed at request time. | |
| message | Yes | ||
| outcome | Yes | ||
| roleName | Yes | ||
| opportunity | Yes |