Kepler CRM

Computes counts, sums, averages, minimums, or maximums over one record type, optionally grouped by a field or a date bucket, with the same filters as list_records. Use for "how many", "per stage", "average fee", "placements per month". Returns exact figures from the database, never estimates. For pipeline questions aggregate applications, not candidates.

Lists the fields of a record type: standard fields, this workspace's custom fields with their slugs, types, allowed options, and whether each can be written, plus the workspace pipeline stages for applications. Call it before filtering on or writing any workspace-specific attribute, and before update_application_stage. Pass writable_only to see only what update_record accepts. No data rows are returned.

Reads one note, call, meeting, email, or other activity in full by id, including body text (HTML notes are returned as plain text with the HTML alongside), links, and version. Use after search_activities when the snippet is not enough, and before update_note.

Returns who you are acting as and the conventions this CRM expects: user id, workspace, role, today's date and timezone, the tools and scopes this connection may use, a short list of domain rules (how "my" resolves, what "candidates in the pipeline" means, how periods are interpreted), and the workspace's own definitions of what its objects mean. Call it once at the start of a conversation and before resolving any relative date or ownership phrase.

Reads the stored results of the most recent matching run for a job: ranked candidates with scores, per-criterion verdicts, evidence, and missing must-haves. It never starts or refreshes a run and has no AI cost. Use it for "why is she ranked first", "who fails a mandatory criterion", or to intersect matches with another attribute. If no run exists it says so; ask the user to run matching in Kepler.

Reads one record in full by exact id: all standard fields, custom fields by slug, version, and the few related rows needed next (a candidate's applications with stage and status, a job's company and open application counts, a list's member ids). Requires an id from a search or list result. Use this before any update so you have expected_version. Never guess an id.

Returns the user's prioritised operational picture in one call: overdue and due-today tasks, stalled submissions, jobs with no recent activity, interviews missing feedback, guarantees expiring, and today's agenda, each with counts and ages. Use for "what needs my attention", "what should I do today", "what am I waiting on". Do not rebuild this from separate searches. Figures in one group apply only to that group.

Returns exact rows of one record type by structured filters and sorts, with a total count. Use for browse or comparison questions with concrete criteria ("open contract jobs in Sydney", "candidates whose notice period is one month"). Field ids and custom-field slugs come from describe_fields; filter values must be ISO dates or option slugs. For fuzzy or CV-content criteria use search_candidates. Pages of 50; follow next_cursor for more.

Searches history: notes, comments, calls, meetings and their summaries, emails, messages, and timeline updates, optionally scoped to one record, actor, type, or date range. Use for "what did we discuss", "when did we last contact", "who said X". Mode exact finds verbatim wording; hybrid (default) ranks by meaning. Each item carries the activity id, type, date, actor, linked records, and a snippet. Summaries are excerpts; read get_activity for the full body.

Finds candidates by meaning across profile, CV text, recruiter notes, and call or meeting summaries. Use for skills, experience, background, or things a candidate said; combine with filters for status, location, owner, or custom fields. Put non-negotiable terms (a company, certification, tool) in must_include to hard-exclude candidates whose corpus lacks them. Returns ranked rows with a snippet showing why each matched. Use list_records instead for exact structured lookups. Bounded to 50 per call; total_count says how many matched.

Cross-type lookup by name, title, email, domain, or free text over jobs, companies, contacts, applications, placements, tasks, and saved lists. Use it to resolve "the Acme role" or "Priya's application" to exact ids before reading or writing. For candidates use search_candidates. Returns up to 25 per call with type, id, label, and a one-line context.