Clera

See how an applyToJob run went. state is running, finished or crashed. When finished, outcome is submitted (sent and confirmed by the employer's site; it is on their tracker as applied), submit_unconfirmed (submit clicked but no confirmation; do not resend), ready_to_submit (a dry run, every field filled, nothing sent), needs_input (nothing sent; ask the candidate each question in needsInput, then call applyToJob again with answers), blocked (a CAPTCHA or login wall, see blockers) or failed (nothing was sent, see blockers for why). A profile_gap question is worth saving to the candidate's profile with editPreferences too. Clera privately records this tool's inputs and results for usage tracking and support.

getApplicationRun

Decline a pending interview invitation from listInterviewRequests. The company is told; give the reason the candidate wants passed on, kept short and plain. Confirm with the candidate first, this cannot be undone here. Clera privately records this tool's inputs and results for usage tracking and support.

declineInterview

Delete one of the candidate's resumes for good. The primary resume and the only resume cannot be deleted; make another one primary first. Confirm with the candidate before calling; there is no undo. Clera privately records this tool's inputs and results for usage tracking and support.

deleteResume

Delete one tailored resume and its PDF for good. The tracked application stays, and applyToJob goes back to sending the candidate's primary resume for that job. Confirm with the candidate before calling; there is no undo, though generateApplicationDocuments can write a new one. Clera privately records this tool's inputs and results for usage tracking and support.

deleteTailoredResume

Remove a job from the candidate's application tracker, with its notes and document links. It does not withdraw anything with the company. Confirm with the candidate before calling. Clera privately records this tool's inputs and results for usage tracking and support.

deleteApplication

Permanently delete the candidate's Clera account and everything Clera holds about them, the same as Delete account on the Account page. It cannot be undone, and this connection stops working right after. Only when the candidate asks to delete their account in this conversation. If they only want fewer messages or a break, offer setEmailSubscription or setJobSearchStatus first. reason is the closest of: found_a_job, no_longer_job_searching, too_many_messages, privacy_concerns, not_the_right_opportunities, other; reasonText is required for other and otherwise optional, in their own words. A confirmation showing what will be deleted is asked before anything happens. Clera privately records this tool's inputs and results for usage tracking and support.

deleteMyAccount

Drafts a LinkedIn connection note and a short email from the candidate to a hiring manager, written from the resume draft in the candidate's voice. Pass the jobId of a Clera role from searchCleraRoles / listMatches to aim them at one role; without it they are general. External board listings from searchJobs have no Clera jobId. Clera privately records this tool's inputs and results for usage tracking and support.

draftOutreach

Create, change or deactivate a company contact. create: needs firstName + email; email is unique per company. Optional lastName, phone, linkedinUrl, title, calendarLink, isPrimary, shouldCc, tagInSlack. 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 or record notes about the company. 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. update_memory: memoryUpdates. Records company-wide notes per topic key (hiring_process, company_culture, communication_preferences, compensation_patterns, deal_breakers): how they hire, what they consistently reject, how they like to be updated. Record a note the moment the contact tells you something durable, without being asked. A null value deletes the key; reuse an existing key instead of adding a near duplicate. Notes about one role go to editJob update_memory. Every note refreshes the hiring rubric Clera uses to pick candidates for this company. 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

Change the candidate's job preferences and profile data, the same fields readPreferences returns. Send only the fields to change; the rest stay as they are. null clears the salary and OTE bounds and the importance fields; every other field is replaced, never cleared. A list field replaces the whole list, so send the complete set; an empty list changes nothing. Companies to block go in add_blocked_companies and remove_blocked_companies by name. For sales, account executive, SDR, BDR and customer success roles, or whenever the candidate mentions OTE, commission or on-target, ask whether their number is base or on-target: a single on-target figure goes in salary_lower_bound with salary_basis "ote"; base and OTE both given go in the salary and ote fields with salary_basis "base". Read the current values with readPreferences first and confirm the change with the candidate before writing; matching reruns on the new values. memory adds or clears the notes Clera keeps about the candidate, five at most. Preferred cities, contact details and resumes are edited on the dashboard, not here. Clera privately records this tool's inputs and results for usage tracking and support.

editPreferences

Replaces one section of the candidate's resume draft with the value sent, and creates the draft if none exists. Sections: profile, work (roles with plain-text bullets, newest first, dates as YYYY-MM, empty endDate means present), education, skills ({name, group}), languages ({name, level}), links ({type, label, url}), design (templateId harvard_classic | ats_clean | executive_serif, accentColor hex, fontSizePt (8–13 in 0.5 steps, 10.5 is standard), sectionOrder, templateOptions). Read the draft first and send the whole section back with your changes; a section is replaced, never merged, so anything you leave out of the value is gone. This is how you rewrite bullets or a summary for the candidate: propose the text, get a yes, then send it here. Clera privately records this tool's inputs and results for usage tracking and support.

editResumeDraft

Fills the candidate's resume draft from data Clera already has: source "profile" is the merged career record (LinkedIn, uploaded resumes and GitHub combined), source "cv" is one parsed uploaded resume (the primary one, or resumeId from listResumes). Only empty sections are filled unless overwrite is true, which replaces what the candidate wrote; confirm before setting it. The result lists which sections were filled; read the draft afterwards and tidy it with editResumeDraft. Clera privately records this tool's inputs and results for usage tracking and support.

seedResumeDraft

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. Results stay within a band around the starting candidate's years of experience. Each result carries a similarity from 0 to 1 for your own screening: a low number means the open pool had nobody close, so say that instead of presenting a weak match as similar, and never show the number to the user. 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

Renders the candidate's resume draft to a PDF and returns a download link that works for an hour. With saveAsCleraResume true the PDF also becomes the candidate's primary resume, the one Clera sends with introductions, and shows up in listResumes. Pass template to switch the design first. Needs a draft with at least a name. Clera privately records this tool's inputs and results for usage tracking and support.

generateResumePdf

Full profile of a candidate already shown to you by searchCandidates, similarCandidates, listPipeline, readShortlist, listRecommendedCandidates or listPendingIntroRequests: the same view as the candidate's page on the Clera dashboard. Triggers: "tell me more about #2", "what did he build at Stripe", any follow-up beyond the card. Resolve talentId from a tool result; never ask for or mention one; no lookup by name. Returns markdown: the candidate's name and LinkedIn URL, identity, preferences, work experience, education, skills, certifications and languages. Never includes contact details, salary, visa status or written summaries; emails, phone numbers and LinkedIn URLs inside descriptions are redacted. 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

Returns the exact Clera dashboard URL for one section of the candidate's own dashboard. One link per request, the one that answers the question; "my dashboard" means home. Commands: list: every link, for when you are unsure which command fits. For you only; never send the menu or several links to the user. home: overview with profile setup and the top matches. matches: the roles Clera matched, with like, pass and the role questions. pipeline: every opportunity by stage, including interviews (withdrawFromProcess withdraws from one). applications: the candidate's own application tracker board (draft, applied, ghosted, interview, offer, rejected), with tailored resumes and cover letters per job. jobs: the wide external job board (searchJobs, saveJob and passJob work on the same data). interview_prep: the interview preparation guide. resume: the resume builder with live preview, plus upload, replace or pick the primary resume. upload_resume: the resume page with the upload box already open, for a file on the candidate's computer. A Google Drive or iCloud share link goes through importResumeFromLink instead. preferences: salary, location, work environment, visa, roles and blocked companies. referral: the referral link, invited friends and earnings. worth: the salary calculator. roast: the profile roast, which needs a PDF upload. perks: partner perks and discounts. interview: interview invitations and feedback. account: login email, profile photo, and the channels Clera reaches them on (email, WhatsApp, iMessage). deleteMyAccount covers account deletion. 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. Clera privately records this tool's inputs and results for usage tracking and support.

getTalentDashboardLink

The profile strength score the Home page shows: 0 to 100, a tier, and the next actions ranked by how many points each adds. A stronger profile matches better and gets introduced more, so the top action is the practical answer to "how do I get more matches". Most actions map to editPreferences or a new resume (importResumeFromLink, or getTalentDashboardLink upload_resume). Clera privately records this tool's inputs and results for usage tracking and support.

getProfileStrength

The candidate's Referral page: their personal share link, how many people they invited and how many signed up in the window, how many visited the link, and the most recent referrals by name. The share link is the thing to hand over when they want to refer someone; it is theirs and safe to send. Clera privately records this tool's inputs and results for usage tracking and support.

getReferralStats

Tell Clera the candidate wants this role, the same as the like button on a Matches card. Works on a match and on an open_role row alike. A like can put the candidate in front of the company: Clera checks the fit against the role, may ask the candidate to answer the role's questions first (listMatches shows them as status questions), and submits them to the company when it fits, which cannot be taken back. Confirm the role with the candidate before liking, and say it went to Clera for review rather than "applied". Pass position and companyName exactly as the row gave them; a mismatch is refused rather than liking the wrong role. Liking twice changes nothing. The dashboard can take up to a minute to show the change. Clera privately records this tool's inputs and results for usage tracking and support.

likeMatch

List the fields the external index can list values for, and optionally the most common values of one field. Free and unlimited — it does not spend an external search. Call it when you are unsure whether a location, industry or seniority value will match anything, then use the exact values it returns. Call it with no field first: that lists the field names this tool accepts. They are index field names and are not the filter keys searchExternalTalent takes, so passing "titles" or "seniorities" here fails. Clera privately records this tool's inputs and results for usage tracking and support.

listExternalTalentFilters

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

The candidate's interview invitations: pending ones waiting for a yes or no, and the history of accepted and declined ones. acceptInterview and declineInterview act on a pending row by its interviewProgressId. Never show the id. Clera privately records this tool's inputs and results for usage tracking and support.

listInterviewRequests

Read the interview tracker updates Clera found in the calendars your team connected (Integrations page, Google Calendar): interviews booked, moved, cancelled or already held with candidates in the pipeline. Use it when the user asks to update their interview tracker, or what changed with their interviews. Each update has a plain label, the candidate, the role, the calendar event, and setInterviewArgs: the exact arguments for setInterview. Never apply an update on your own. Show the user the list, ask which to apply, then call setInterview once per confirmed update with its setInterviewArgs. Scheduling or advancing sends the candidate prep reminders, so say that before they confirm. An empty list means no calendar is connected or every interview already matches the tracker; point the user to the Integrations page if nobody connected a calendar yet. Clera privately records this tool's inputs and results for usage tracking and support.

listTrackerUpdates

The 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. 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.

listMatches

The candidate's Pipeline page: every opportunity Clera has for them, in every state, with the interview date where one is booked. status: new (not reacted yet), questions (liked, company questions still open), interested (liked, Clera is working on it), not_submitted (liked, Clera reviewed it and did not put them forward), process (submitted to the company or interviewing), declined (candidate passed), withdrawn, no_match (Clera or the company said no), closed (the role closed). A not_submitted or no_match row carries reason: relay it as the why. undoMatchDecision reverses a declined row. Never show opportunityId or jobId. Jobs the candidate applied to outside Clera are not here; they live on the application tracker (listApplications). Clera privately records this tool's inputs and results for usage tracking and support.

listMyPipeline

The candidate's uploaded resumes, newest first, with which one is primary (the one Clera sends with introductions), plus the AI resume feedback if it has been generated: an overall and an ATS score, each out of 10, a summary, strengths and concrete improvements. Add a new resume with importResumeFromLink (a Google Drive or iCloud share link) or getTalentDashboardLink upload_resume (a file on their computer). setPrimaryResume, deleteResume and refreshResumeFeedback act on what is here. Clera privately records this tool's inputs and results for usage tracking and support.

listResumes

The resumes Clera tailored to the candidate's tracked applications (generateApplicationDocuments with kinds resume), newest edit first: each with its draftId, the applicationId it belongs to (listApplications), the match score for that role before and after tailoring (0-100 with a band), how many rewrites it kept and when the candidate last reviewed it. applyToJob sends the tailored resume for that application's job. getTailoredResume shows every change and the PDF. Clera privately records this tool's inputs and results for usage tracking and support.

listTailoredResumes

List the outreach your company has asked Clera to run with requestOutreach, newest first, with where each one stands: being prepared, live, or failed. Clera privately records this tool's inputs and results for usage tracking and support.

listOutreachRequests

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 one page at a time. When hasMore is true, pass nextCursor as cursor to get the next page. 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 one page at a time. When hasMore is true, pass nextCursor as cursor to get the next page. Clera privately records this tool's inputs and results for usage tracking and support.

listPendingIntroRequests

List the job board listings saved so far, newest first. Listings that have closed since they were saved are still here, with isLive false — they are kept on purpose rather than disappearing. Point them out and offer to search for something close instead. applyToJob with a row's jobId applies for them. Clera privately records this tool's inputs and results for usage tracking and support.

listSavedJobs

List the criteria presets your team saved in People Search, newest first, each with its name and criteria. Reuse a preset's criteria when the user asks for a search like one they ran before. Clera privately records this tool's inputs and results for usage tracking and support.

listSearchPresets

List the email and LinkedIn sequences you can see (your team's shared ones and your own), most recently edited first, with step count and how many people are enrolled, active, opened, replied and interested. Clera privately records this tool's inputs and results for usage tracking and support.

listSequences

List this company's team members on Clera plus any pending email invitations. Returns each member's name, email, and role, and each pending invite's email, role, and invited date. Roles are owner, editor, or viewer. No internal ids are returned; refer to people by name or email. Use this to check who already has access before inviting someone, so you don't re-invite an existing member or duplicate a pending invitation. Clera privately records this tool's inputs and results for usage tracking and support.

listTeamMembers

List the company's hiring pipeline, the same board the Pipeline page of the dashboard renders: every candidate grouped by stage, with a count per stage. Stages in order: review (awaiting the company's review), intro_requested (intro in progress), introduced (awaiting first interview), interviewing, offer, hired. Each candidate includes opportunityId, talentId, talentName, roleId, roleName, and for interviewing candidates interviewStage (e.g. "Technical screen (2 of 3)") and nextInterviewAt. roleCounts gives the board total per role, largest first. It is the only candidate count per role; the job tool's list command carries none. Use it for any question about how many candidates are in the pipeline, how many a role has, who is interviewing, or which stage someone is at. To decline someone already in the pipeline, pass their opportunityId, talentName and roleName to passCandidate; a review row with a null opportunityId is declined from listRecommendedCandidates instead. Counts cover the whole stage, candidates are capped by candidatesPerStage. Clera privately records this tool's inputs and results for usage tracking and support.

listPipeline

List the jobs the candidate applied to or plans to apply to, from the external job board, a posting link or typed by hand: their application tracker, newest first, with each one's stage (draft, applied, ghosted, interview, offer, rejected), notes and links to any tailored resume (tailoredResume: draftId, fit before and after) or cover letter. applicationState says where an applyToJob send stands (sending, sent, unconfirmed, needs_answers, not_sent, tracked); pendingQuestions are the employer's questions still waiting on the candidate. That is also how to pick up an application whose runId got lost: ask those questions and call applyToJob with its applicationId and answers. summary counts, across the whole board, what was sent and confirmed in the last 24 hours, what is sending, what was submitted but not confirmed, what needs the candidate's answers or OK, and what couldn't be sent; autoApplyRunsLeftToday is how many more applyToJob sends fit in the rolling 24 hours. The tracker is the candidate's own record of jobs they are applying to anywhere, not Clera intros. Moving a card never contacts the company. Document links expire after an hour; list again for fresh ones. Clera privately records this tool's inputs and results for usage tracking and support.

listApplications

Resolve real, indexed values for searchCandidates filters before using them. work_history and education_history only match EXACT company/school names; always resolve the user's phrasing ('Figma', 'TUM', 'Stanford') to indexed values with this tool first, then pass those values to searchCandidates as plain filters or boolean_tags. Clera privately records this tool's inputs and results for usage tracking and support.

suggestFilterValues

Create, rename, delete or switch the default of the candidate's resume-builder versions, the same as the versions menu on the dashboard resume page. create makes an empty version, or a copy of draftId; rename and make_default take draftId and, for rename, name; delete removes a version that isn't the default, together with its PDF. Take draftIds from readResumeDraft. The default version is what readResumeDraft, editResumeDraft and generateResumePdf use when no draftId is passed. Confirm a delete with the candidate first. Clera privately records this tool's inputs and results for usage tracking and support.

manageResumeVersions

Pass on a candidate for a specific role. Use this when the company decides a candidate is not a fit, from a search result, from listPendingIntroRequests or listRecommendedCandidates, or someone already in the pipeline (introduced, interviewing or at offer) from listPipeline. Target either a candidate from searchCandidates or similarCandidates (talentId, with jobId or the interactive role picker), or a list entry (its opportunityId, with talentName and roleName copied verbatim from that entry; all three must describe one entry). If the candidate and role you were asked about are not on the page you fetched, re-call the same list with roleId to narrow, or with offset or a larger candidatesPerStage to page further; if the pair does not exist, say so and pass on nothing. Passing a different role for the same candidate is refused. Requires a noFitCategory and a specific reason naming what this candidate misses. This marks the opportunity as no_fit (creating the opportunity record first when the candidate came straight from search) and logs the company's decision with their feedback. Clera privately records this tool's inputs and results for usage tracking and support.

passCandidate