JobHawk

Use this when the user wants to record or remember something they were told about a job they already track in JobHawk, such as a recruiter's name, interview feedback, a salary discussion, or a follow-up date. This includes reporting what an employer or recruiter said without using the word 'note', such as a timeline or next step the recruiter gave. Identify the application by application_id or by company_name and job_title; if more than one matches, this returns the candidates so you can ask the user which one. The note is appended with today's date and never replaces earlier notes. It does not change the application's status (use jobhawk_update_application_status for that), and it is not for general reminders or notes unrelated to a tracked application. Requires a connected JobHawk account.

jobhawk_add_note

Use this when the user asks what jobs they are tracking or have applied to, wants an overview of their job search, or asks about their applications at a specific company. Optional filters: status (one or more of wishlist, applied, screening, interview, offer, accepted, rejected, ghosted, withdrawn), company (matches part of the company name), and limit (default 20, max 50). Returns each application's id, company, job title, status, and last update, the count of applications in each status, and whether more results exist; it never returns posting text or notes. Read-only: it changes nothing. Do not use this to save a job (use jobhawk_save_job), to change a status (use jobhawk_update_application_status), or for upcoming interviews and follow-ups (use jobhawk_whats_coming_up). Requires a connected JobHawk account; an empty list means nothing matches.

jobhawk_list_applications

Use this when the user wants to save, track, log, or keep tabs on a specific job posting or application in JobHawk, including phrasing that never says 'JobHawk' or 'save' at all, such as 'hold onto this one for me', 'add this job', or 'I just applied here, log it'. Given a posting URL, pass it directly as url and call this tool with whatever job title and company name the user has stated; never fetch or read the page first to check it before saving. If only a URL is given and the title or company isn't stated, ask the user for them rather than fetching the page. Pass what you can read from the posting: job_title and company_name are required; url, location, salary_min and salary_max (whole annual amounts, only if stated), employment_type, and job_description are optional; status defaults to wishlist, and use applied if the user says they already applied. Do not use this to change the status of a job that is already saved (use jobhawk_update_application_status), to add a note to one (use jobhawk_add_note), or for jobs the user is only discussing or asking about rather than asking to track. If the user's JobHawk account is not connected, this returns a preview and saves nothing; set link_account to true only when the user asks to connect JobHawk to save it, which asks them to sign in. When connected it creates one tracker entry, or returns the existing entry if the same posting URL is already saved. It never applies to the job for the user.

jobhawk_save_job

Use this when the user reports progress or an outcome on a job they already track in JobHawk, such as 'I applied', 'I have an interview', 'they rejected me', 'I got an offer', or 'I'm withdrawing'. This includes a plain statement of what happened for a named application, with no explicit request to 'update' or 'change status' anywhere in it: treat it as an implicit request to update that application rather than as conversation to just acknowledge, as long as the outcome has already happened, not a plan, hope, or hypothetical. Identify the application by application_id (from jobhawk_list_applications or jobhawk_save_job) or by company_name and job_title; if more than one application matches, this returns the candidates so you can ask the user which one, and it never guesses. If only one application partially matches the names, that one is updated; when unsure, confirm the application with the user before calling. One of wishlist, applied, screening, interview, offer, accepted, rejected, ghosted, withdrawn. Use screening for a recruiter or phone screen and interview for any interview round. It overwrites the current status and returns the previous and new status; setting the same status again changes nothing. Do not use this to save a new job (use jobhawk_save_job). Requires a connected JobHawk account.

jobhawk_update_application_status

Use this when the user asks what is coming up in their job search, including questions that sound like calendar questions but are about interviews or follow-ups, such as 'when is my next interview' or 'what follow-ups are due'. JobHawk, not the user's general calendar, is the source for interview and follow-up scheduling tracked here. A general question about the user's calendar or week that doesn't mention interviews, applications, or follow-ups is not for this tool. Returns scheduled interviews and pending follow-up reminders from JobHawk within the next `days` days (default 7, max 30), each with its date, type, title, and the related company and job when there is one. Read-only: it never creates, moves, or cancels anything. Requires a connected JobHawk account; an empty list means nothing is scheduled.

jobhawk_whats_coming_up