Mark a person yes or no
setRoleSearchDecisionMark one person a Search found (person id from getRoleSearch) as a yes or no for the role, with up to 5 short reasons. On a normal Search it only records the call: nobody is contacted, introduced, shortlisted or passed, and the next run learns from it. On the Sourcing feed of a role (people Clera's sourcing run approved and has not contacted yet), a yes contacts a real person: Clera finds their email and starts outreach for the role, or puts them on the LinkedIn queue when no email is found. Make a yes there only when the user explicitly asks to reach out to that person, and say first that it starts outreach; a no contacts nobody and frees the person for Clera's other roles. A call is final: once anyone on the team has marked a person, it can't be changed, and only Searches with a role take calls. Use the user's own call and reasons, never decide for them, and read the call back to them before making it.
Clera privately records this tool's inputs and results for usage tracking and support.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"roleSearchId": "<roleSearchId>",
"roleSearchPersonId": "<roleSearchPersonId>",
"decision": "<decision>"
},
"name": "setRoleSearchDecision"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| orgId | No | Organization to act as. Only needed when you belong to more than one organization. | |
| reasons | No | ||
| decision | Yes | ||
| roleSearchId | Yes | ||
| roleSearchPersonId | Yes |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| run | Yes | ||
| decision | Yes | ||
| outreachNote | Yes | ||
| feedbackLedgerId | Yes | ||
| roleSearchPersonId | Yes |