Noon

Accept a candidate from the role's feed: adds them to the project, syncs to the ATS, and (when the role has auto-contact on) queues them for outreach. Get candidate_id from get_candidate_feed.

accept_candidate

Aggregate a role's sourcing pipeline for investigation. group_by="event" gives the funnel counts (reviewed, accepted, rejected, added to project); group_by="day"|"week"|"month" gives a time series of activity (pass events=["suggested"] to chart when candidates were reviewed); group_by="company" ranks the source companies of the reviewed candidate pool; group_by="rejection_reason" gives rejection categories (Company, Seniority, Location, Education, Skills, Experience, Criteria, …). For outreach, events=["contacted"] counts candidates whose first message was actually sent, dated by that send (group_by="day" gives daily contacted); replies are interested / not_interested / invite_accepted. Optional since/until are ISO timestamps. Compose several calls to investigate — e.g. get_role_state first, then group_by="event" for the funnel, then group_by="rejection_reason" to see what is filtering people out. Get role_id from list_roles.

query_events

What is constraining a role's search: rejection reasons by category, PLUS the sole-blocker criteria — for each must-have, how many candidates fail ONLY that one (sole_blocker ≈ how many otherwise-qualified people you would recover by relaxing it). This is the highest-signal tool for "how do we widen the pool without dropping quality". Optionally scope to one company (e.g. "why were the Stripe people rejected?") via company or company_id. Get role_id from list_roles.

rejection_analysis

Write the outreach sequence for a role — replaces ALL existing steps, so pass the complete sequence (fetch it first with get_outbound_sequence when editing). Steps run in order: the first sends when outreach starts, each later step waits wait_days after the previous one. Message placeholders that auto-fill per candidate: {first_name}, {last_name}, {company}, {ai_intro} (an AI-personalized intro line — use it on the first InMail and the first email, since candidates often miss InMail but still see email). A typical sequence: connection invite → InMail 2 days later → 2-3 email follow-ups. Omit connection_accepted to keep the role's existing connection-accepted trigger; pass null to disable it.

update_outbound_sequence

Diagnose whether a small/slow pool is caused by the SEARCH filters or by post-search EVALUATION. Runs loosened search probes (looser titles, wider location, wider experience, broader company targeting, looser must-haves) and reports how many candidates each would add (strongest_levers), alongside the accepted/rejected/added funnel, active relaxations, recent automatic search adjustments, and the top rejection bottlenecks. Use for "why is the pool small", "are filters too tight", "why did this relax", "what should we loosen". Get role_id from list_roles.

pool_diagnostics

The recruiter-facing AI evaluation summary (why a candidate was accepted or rejected) by candidate_id. Returns only the sanitized text shown in the product — internal scoring, rubrics, and prompts are never exposed. Get candidate_id from find_candidates. Get role_id from list_roles.

explain_candidate

List individual candidates for a role, filtered by name (partial), current company, decision (reviewed | accepted | rejected | added; default reviewed), and company_fit_rating (0=best fit … 4=worst). Returns name, title, company, fit, and a rejection reason when decision="rejected". Keyset-paginated: pass the returned next_cursor as "after". Use for "find <person>", "who from <company> got rejected", "show the accepted candidates", or to gather a cohort to compare. Get role_id from list_roles.

find_candidates

Full profile for one candidate (current company, title, location, years of experience, work history, education, skills, company fit) by candidate_id. Get candidate_id from find_candidates. Get role_id from list_roles.

get_candidate

Read a role's current outreach sequence: the ordered steps (LinkedIn connection invite, InMail, emails) with their wait times and message copy, plus the connection-accepted trigger messages. Call this before update_outbound_sequence when editing an existing sequence.

get_outbound_sequence

A diagnostic snapshot of one role's sourcing: whether it is currently running, its configuration (enabled / calibrating / paused at the sourcing cap / disabled), the sourcing cap, the must-have criteria, which evaluation relaxations are active, the search settings (titles, locations, experience, location radius, company restrictions), and how many candidates the search has reviewed so far. Call this FIRST for any question about how a role's search is doing, why it is/isn't producing candidates, or before proposing changes. reviewed_total counts candidates the search considered — not candidates delivered to the recruiter (funnel: reviewed -> accepted/rejected -> added to project). Get role_id from list_roles.

get_role_state