Clera

Record a candidate the company liked as a good-fit example for a job. When a company expresses positive feedback about a candidate, add their LinkedIn to the job's good-fit list. These examples improve future candidate matching. Input (provide at least one of linkedinUrl or talentId): - jobId: Which job this good-fit example is for (resolve with the job tool's list command) - linkedinUrl: Direct LinkedIn URL. If the source text wraps it in link markup (e.g. <https://linkedin.com/in/name|Display Name>), extract just the URL - talentId: UUID of the talent, their LinkedIn URL will be resolved automatically If the URL is already in the list, returns success with a note instead of erroring. Returns a refusal if the jobId doesn't belong to this company. Clera privately records this tool's inputs and results for usage tracking and support.

addGoodFitExample

Create and edit the company's roles. create: one of position (blank role), jobUrl (posting link) or jobText (pasted JD). Returns the jobId. Only when the user explicitly asks for a new role. Then run get, say which fields are missing, and hand over the getDashboardLink role_preview link. update: jobId + updates. Basic fields incl. the candidate-facing description, lifecycle (open publishes and starts matching), pay, experience, visa, workplace, hiringManagerContactId. Only provided fields change; matching needs employmentType, a salary bound and an experience bound. set_brief: jobId + brief. Markdown sourcing brief for Clera's matching team, never shown to candidates; full replace, null clears. set_roles: jobId + roles. 1 to 5 job-category tags, e.g. ["Account Executive", "AE", "Sales"]. Required for matching. set_stages: jobId + stages. Ordered interview stages, full replace. add_requirements: jobId + requirements. Discrete, evaluable criteria the contact stated, e.g. "must have payments experience". Appends; vague preferences go to update_memory. update_memory: jobId + memoryUpdates. Notes per topic (ideal_candidate, interview_process, team_dynamics, selling_points, urgency). Null deletes a key; reuse keys over near duplicates. create_question: jobId + question and optional fields. Returns the full list. update_question: jobId + questionId + fields to change. Returns the full list. delete_question: jobId + questionId. Returns the full list. set_requirements: jobId + requirements. Full replace of the active requirements; omitted ones are removed. Returns the resulting list. add_location: jobId + normalizedLocation, e.g. 'Berlin, Germany', geocoded strictly; reformulate if rejected. add_remote_location: jobId + code. 'worldwide', a region or country slug, for remote roles. remove_location: jobId + locationId. Location commands return the full list with ids. jobId comes from readJob list or create; question and location ids from readJob list_questions and list_locations. Clera privately records this tool's inputs and results for usage tracking and support.

editJob

Create, change or deactivate a company contact. create: needs firstName + email; email is unique per company. Optional lastName, phone, linkedinUrl, title, calendarLink, isPrimary, shouldCc. Re-adding a removed email reactivates it. update: contactId + any fields to change. delete: contactId. Deactivates the contact (soft delete). set_primary: contactId. Makes it the company's primary contact. set_active: contactId + active. Reactivate (true) or deactivate (false). Ids come from readCompanyContacts list. calendarLink decides whose calendar the hiring manager's interview books on, so keep it correct. Clera privately records this tool's inputs and results for usage tracking and support.

editCompanyContact

Update the company profile. update: writes the fields you pass. Omitted fields are left untouched. The four long-text fields (description, descriptionShort, about, culture) are written only when they are currently blank, so an existing value is never overwritten by default; every other field overwrites unconditionally. With overwrite=true it also replaces already-filled long-text fields; pass overwrite only when the user explicitly asks to replace or rewrite an existing value. Always run readCompanyProfile get before update so you do not resend values that are already set. Clera privately records this tool's inputs and results for usage tracking and support.

editCompanyProfile

Given one candidate your company has already been shown, return other candidates whose profiles are closest to theirs, ranked by similarity. Use it when someone likes a specific profile and wants more of the same, and after requestIntro to keep the shortlist moving. Chain it: run it again on a result to walk further from the original person. Similarity is computed from the whole profile (role, skills, experience and domain), not from filters, so this takes no search criteria; use searchCandidates when the ask is a requirement rather than a resemblance. The same exclusions as searchCandidates apply, so people already shown to your company, your own employees, and people who work at Clera never come back, and the starting candidate is never in their own results. Clera privately records this tool's inputs and results for usage tracking and support.

similarCandidates

Full profile of a candidate already shown via searchCandidates, listRecommendedCandidates, or listPendingIntroRequests. Triggers: "tell me more about #2", "why is she a good fit", "what did he build at Stripe", any follow-up beyond the card. Works for candidates previously identified to your company, including historical named shares even after the share expires or is revoked. A candidate whose identity is still hidden from your company is refused; offer requestIntro. Resolve talentId from a tool result; never ask for or mention one; no lookup by name. Returns markdown: identity, career highlights, professional + AI summary, work experience, education, skills, certifications, languages, publications & awards. Use it to reason about fit. Omits structured contact fields and labeled salary and visa preference lines. Professional summaries and career descriptions may contain personal details supplied in free text. Clera privately records this tool's inputs and results for usage tracking and support.

getCandidateProfile

Returns the exact Clera dashboard URL for one section of this company's dashboard. One link per request, the one that answers the question; "my dashboard" means review. Commands: list: every link available to this company, for when you are unsure which command fits. For you only; never send the menu or several links to the user. review: the candidate review page. roleId scopes it to one role; talentId with it opens that candidate. pipeline: every candidate in process. roleId scopes it to one role; talentId with it opens that candidate. roles: the role list page. role_create: the create-a-role page. role_preview: the role as candidates will see it, with an edit button. Requires roleId. Hand it over after creating a role so the user can check how it reads. role_edit: the internal role editor. Requires roleId. role_public: the public job posting. Requires roleId; refuses when the role has no public posting. talent_search: the talent search page. Only available when Clera has enabled talent search for this company. settings_company: company profile settings, the public company information shown to candidates. settings_members: team member settings. invite true, optionally with email, opens the invite popup ready to send; Clera never sends team invites itself. settings_contacts: the company contacts settings page. settings_profile: the user's own personal profile, name and avatar only. This tool is the only source of Clera dashboard links. Never construct, guess, shorten or modify a getclera.com URL; copy the URL from this tool's output verbatim. There is no app.clera.io domain and no /org path. Clera privately records this tool's inputs and results for usage tracking and support.

getDashboardLink

List valid values (with candidate counts) for searchCandidates filters. Returns only the requested fields, keeping the response small. Use this to discover which role_names, skills, job_types, preferred_work, countries, or languages are available before searching. work_history and education_history are too large to list here; use suggestFilterValues for those. Clera privately records this tool's inputs and results for usage tracking and support.

listFilterOptions

List candidates the company has passed on (declined) for its open roles. Use this when the company wants to see who was passed, or asks to undo a pass. Each item includes opportunityId, talentId, talentName, roleName, and passedAt. passedAt is the opportunity's latest update time and may differ from when the pass happened. opportunityId is a tool input only, pass it to undoPass to undo a pass. Never show it to the user; refer to the candidate by name. Returns paginated results, use limit and offset for more. Clera privately records this tool's inputs and results for usage tracking and support.

listPassed

List candidates who have expressed interest in the company's roles and are waiting for a company decision, the intro requests shown in the Review tab of the dashboard. Each item includes opportunityId, talentId, talentName, talentOneliner (summary), and roleName. opportunityId is a tool input only, pass it to requestIntro or passCandidate. Never show it to the user; refer to the candidate by name. Returns paginated results, use limit and offset for more. Clera privately records this tool's inputs and results for usage tracking and support.

listPendingIntroRequests