Search roles with Clera
searchCleraRolesSearch the open roles at startups Clera works with. Every result is a role Clera can introduce the candidate to, so this is the first search to run whenever they want roles, a company or a stack. When nothing here fits, run searchJobs straight away and show those; don't ask first.
Keep query to keywords — a title or a stack — not a sentence; leave it empty to browse newest first. When the candidate names a company, put it in company: the search then covers that company's open roles only, and an empty result means Clera has nothing open there. arrangement is remote, hybrid or on-site and widens to compatible roles the way Clera's own job matching does: hybrid also returns remote roles, on-site also returns hybrid ones, and each row's arrangement says what the role actually is. cities are exact, as the candidate names them, and countries keep roles in those countries; minSalary keeps roles with no salary on file, so an unknown salary is a question to ask, not a miss. Ranking follows the candidate's role affinity, the roles they hold and adjacent ones, and roles they declined stay hidden (undoMatchDecision brings one back).
jobFacts filters on what each role's text says (visa sponsorship, OPT/CPT, TN, citizenship or clearance, years required, languages, relocation, travel, on-call, people management, AI product, commission-only pay). Set the ones that follow from what the candidate told you, like needsVisaSponsorship for someone who needs a visa; roles that don't say stay in.
status is null until the role is one of the candidate's opportunities; otherwise it is the status listMatches shows, and introRequested true means the company already asked for them. likeMatch with the row's jobId, position and companyName tells Clera they want it, and Clera may submit them to the company when it fits. readJobListing with the row's jobId has the full description. Never show 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": "searchCleraRoles"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| query | No | Keywords: a job title, a stack or a skill. Not a sentence; a company name goes in company. | |
| cities | No | Cities as the role lists them, like Berlin or London. | |
| cursor | No | Pass nextCursor from a previous call to get the next page. | |
| company | No | A company name as the talent says it. Only that company's open roles come back. | |
| perPage | No | ||
| jobFacts | No | Filters on facts read from each posting's text. | |
| countries | No | Country names, like "Germany" or "United States". | |
| minSalary | No | Yearly figure in the role's own currency. Roles with no salary on file stay in. | |
| arrangement | No | Widens the way Clera's matching does: hybrid also returns remote roles, on-site also hybrid ones. | |
| visaSponsorship | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| found | Yes | ||
| roles | Yes | ||
| hasMore | Yes | ||
| nextCursor | Yes |