add_candidate
ChatGPTUse this when the user wants to add someone they found or were referred to as a candidate for a job and has no resume file. Creates a new candidate on a position in Breezy HR. Requires name. email_address is required when origin is "applied". Use add_candidate_by_resume if you have a resume file to parse instead.
add_candidate_by_resume
ChatGPTUse this when the user has a resume file and wants to add that person as a candidate for a job. Creates a new candidate by uploading and parsing a resume file. The resume bytes must be base64-encoded. Supported formats: pdf, doc, docx, txt, rtf, html.
add_candidate_document
ChatGPTAttach a document file to an existing candidate. The file bytes must be base64-encoded. Per Breezy docs, this is also how you add a resume to an existing candidate.
add_candidate_scorecard
ChatGPTUse this when the user wants to rate a candidate or record a hiring vote ("strong yes on Elena"). Adds a scorecard rating for a candidate. Score must be one of: very_good, good, neutral, poor, very_poor.
add_position
ChatGPTCreate a new position (job opening) in Breezy HR.
compare_candidates
ChatGPTUse this when the user wants to compare two to five candidates for the same job side by side. Shows stage, score, current role, experience, education and source for each.
draft_job_post
ChatGPTUse this when someone wants to hire for a role, or to write, draft or improve a job post or job description. Works without a Breezy account. You write the complete post (title, description, employment type, location and pay range); this tool checks it against the fields Breezy accepts and shows the user an editable draft. Nothing is saved. Call it first even when the user says they want to post a job: they review the draft before anything goes live. Do not use it to change a job that already exists in Breezy; use update_position for that.
get_candidate
ChatGPTGet full details for a specific candidate including work history, education, social profiles, cover letter, and custom attributes. Use this when you need complete candidate information beyond what list_candidates returns.
get_candidate_assessments
ChatGPTGet third-party assessment results for a specific candidate.
get_candidate_background_checks
ChatGPTGet background check results for a specific candidate.
get_candidate_conversation
ChatGPTGet the conversation history for a specific candidate including messages between the candidate and hiring team.
get_candidate_custom_attributes
ChatGPTGet the custom attribute definitions for candidates in a Breezy HR company.
get_candidate_custom_fields
ChatGPTGet custom field values for a specific candidate.
get_candidate_documents
ChatGPTGet documents attached to a specific candidate.
get_candidate_meta
ChatGPTGet rich metadata for a candidate including notes, scorecards, tasks, interviews, documents, and conversation history.
get_candidate_questionnaires
ChatGPTGet questionnaires and responses for a specific candidate.
get_candidate_resume
ChatGPTUse this to read a candidate's resume. Returns the resume's text for PDF resumes, the most common format; for other formats, only the file type and size, since their text can't be read here. The details Breezy parsed from the resume (work history, education, summary) are in get_candidate.
get_candidate_stream
ChatGPTGet the activity stream for a specific candidate including notes, stage changes, and other events. Returns one page of 50 events. To read further back, call again with skip set to the number of events already received (50, 100, ...); the oldest event in the history carries first_activity: true, so a page containing it is the last one.
get_company
ChatGPTGet details for a specific Breezy HR company by ID. Use list_companies first to get available company IDs.
get_company_questionnaire
ChatGPTGet details for a specific company questionnaire including its questions.
get_company_template
ChatGPTGet details for a specific company email template.
get_pipeline
ChatGPTGet the stages for a specific pipeline. Returns { pipeline_id, stages: [...] }. Use list_pipelines first to get pipeline IDs and see all pipelines at once. Stage id values (e.g. "applied", "interviewing") are what set_candidate_stage and move_candidate expect.
get_position
ChatGPTGet details for a specific position (job opening) in Breezy HR.
get_position_custom_attributes
ChatGPTGet the custom attribute definitions for positions in a Breezy HR company.
get_position_custom_fields
ChatGPTGet custom fields defined on a specific position in Breezy HR.
get_position_stream
ChatGPTGet the activity stream for a specific position in Breezy HR. Returns one page of 30 events, newest first. To read further back, call again with skip set to the number of events already received (30, 60, ...); a page with fewer than 30 events is the last one.
get_position_team
ChatGPTGet team members assigned to a specific position in Breezy HR.
get_user
ChatGPTGet the currently authenticated Breezy HR user.
get_user_details
ChatGPTList the companies the authenticated Breezy HR user belongs to, with each company's ID, name, friendly_id and its position and member counts. Use list_positions, get_position_team, list_pipelines and the other company tools for the details.
list_candidates
ChatGPTUse this to read who applied to a job for your own reasoning, such as counting applicants or finding a candidate by name. Lists candidates for a position in Breezy HR. Returns up to page_size candidates (default 50) with summary fields per candidate (name, email, stage, source, scores, tags); page through with page until a page comes back short. Pass stage_id to get only the candidates in one pipeline stage; the filter is applied server-side. For full details including work history, education, social profiles, and custom attributes use get_candidate. Requires a company_id and position_id. Use list_companies and list_positions to find these IDs.
list_companies
ChatGPTList all companies available to the authenticated Breezy HR user. Returns company IDs needed for other API calls.
list_company_questionnaires
ChatGPTList questionnaires available for a Breezy HR company.
list_company_templates
ChatGPTList email templates available for a Breezy HR company.
list_pipelines
ChatGPTList all pipelines for a Breezy HR company. Returns an array of pipeline objects each containing a stages array. Stage id values (e.g. "applied", "interviewing") are what set_candidate_stage and move_candidate expect.
list_positions
ChatGPTUse this when the user asks about their jobs or job openings ("what jobs do I have open", "my line cook job"), or to find the position_id another tool needs. Lists positions (job openings) for a Breezy HR company. Use list_companies first to get a company_id.
move_candidate
ChatGPTUse this when a candidate should be considered for a different job. Moves a candidate from one position to another. Requires the target position ID and target stage ID. To change their stage in the same job, use set_candidate_stage. The move is refused if a candidate with the same email address is already on the target position.
post_candidate_message
ChatGPTUse this when the user wants to contact a candidate, for example to ask their availability, invite them to interview or follow up. Sends a message to a candidate via the conversation thread. This message is visible to the candidate.
post_candidate_note
ChatGPTUse this when the user wants to record feedback or a private note about a candidate, such as interview impressions. Adds an internal note to a candidate's activity stream. Notes are visible to the hiring team only, never to the candidate.
publish_job
ChatGPTUse this only after the user has reviewed a draft from draft_job_post and then, in a later message, asked to post or publish it. Asking to post a job at the start of a conversation is not that: draft it first. Creates the position in their Breezy company, including the pay range, and publishes it to the company careers page. Pass the draft as the user last saw it, with their edits. Leave company_id out unless the user named a company: if they belong to more than one, the tool shows them their companies to pick from. Call it once per job (a call that only shows the company picker posts nothing): if Breezy does not know the draft's department or category, the job is still posted without it and the reply says so; never call it again for the same job and never swap in a different department or category without asking the user. Do not use it to change a job that already exists; use update_position.
search_candidates
ChatGPTUse this when you have a candidate's email address and need to find them across every job in a company. Searches by email address only; to find a candidate by name, use list_candidates on their job.
send_candidate_questionnaire
ChatGPTUse this when the user wants a candidate to answer screening or follow-up questions. Sends a questionnaire to a candidate. Use list_company_questionnaires to find questionnaire IDs.
set_ai_scoring
ChatGPTUse this only when the user asks to turn AI candidate scoring on or off for a job. When on, Breezy scores each new applicant against the job (0 to 10 with a recommendation) within about a minute of applying, using the account's AI credits. Candidates who already applied are not scored. Never turn it on without the user asking.
set_candidate_stage
ChatGPTUse this when the user wants to move a candidate forward or back in the hiring process, for example to interviewing, offer or hired, or to reject them (disqualified). Moves a candidate to a different pipeline stage. Use get_pipeline to see available stage IDs.
set_position_state
ChatGPTUse this when the user wants to open, close or archive a job, for example once the role is filled. Changes the state of a position (e.g. publish, close, archive, draft).
show_candidate
ChatGPTUse this when the user wants to look at one candidate: their profile, experience, education, stage and score. The profile has a stage picker the user can move them with directly. If the user also asks to move this candidate, call set_candidate_stage first and this tool after it, so the profile shows the new stage. Use get_candidate instead when you need the full record for your own reasoning.
show_candidates
ChatGPTUse this when the user wants to see, review or triage the candidates for a job, optionally in one pipeline stage (for example "who applied to the line cook job this week" or "show me everyone in interviewing"). Shows them as a list the user can pick from to view or compare. Use list_candidates instead when you need the data for your own reasoning and the user did not ask to see the candidates.
update_candidate
ChatGPTUpdate fields on a candidate. Can change name, email, phone, summary, headline, address, tags, social profiles, source, and cover letter.
update_candidate_custom_attribute
ChatGPTSet a custom attribute on a candidate. Custom attributes are name/value string pairs.
update_candidate_custom_field
ChatGPTUpdate a custom field value on a candidate. Use get_candidate_custom_fields to see available fields and get_candidate_custom_attributes (company level) for field definitions.
update_candidate_education
ChatGPTUpdate education for a candidate. Requires school_name at minimum. Optional: degree, field_of_study, start_year, end_year.
update_candidate_questionnaire
ChatGPTSubmit responses for a candidate questionnaire. Use get_candidate_questionnaires to see pending questionnaires and their question IDs.
update_candidate_work_history
ChatGPTUpdate work history for a candidate. Requires company_name at minimum. Optional: title, summary, start_year, start_month, end_year, end_month.
update_position
ChatGPTUse this when the user wants to change a job that already exists, such as its title, description, pay or location. Updates an existing position in Breezy HR. Only include fields you want to change.
update_position_custom_field
ChatGPTUpdate a custom field value on a position. Use get_position_custom_fields to see available fields.
