List my matches
listMatchesThe top of the candidate's Matches page, in the order the page shows them: companies that asked to talk to them, their active roles, then the first 50 roles of their ranked list. A ranked role Clera hasn't written up for them yet is kind open_role, with no whyMatch. total is how many roles the whole page holds and pendingCount how many still wait on the candidate; the page itself scrolls past the rows returned here.
Rows with introRequested true are companies that asked to talk to this candidate; they come first. A row with applyOwnership referral_link (via partnerLabel, e.g. micro1) gets no intro: liking it hands the candidate referralUrl to apply on the partner's own site, and those roles sit at the bottom of the list. status questions means the candidate liked the role and the company still needs answers to its questions — answerRoleQuestion handles those. Roles already passed on, closed or marked no match are not here; listMyPipeline has everything.
Act on a row with likeMatch or declineMatch (jobId, position and companyName from the row). For the full role, readMatch takes the row's opportunityId; an open_role row has none, so readJobListing takes its jobId. Never show opportunityId or jobId.
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": "listMatches"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| total | Yes | ||
| matches | Yes | ||
| pendingCount | Yes | ||
| introRequestCount | Yes | ||
| openQuestionCount | Yes |