GigHQ.ai
Job-search tracker for AI agents: applications, stale follow-ups, skills gaps, H-1B lookup.
| Endpoint | https://mcp.gighq.ai/mcp (streamable-http) |
|---|---|
| Registry version | 1.0.0 |
| Now | 34 tools · grade F (39) · pin ts_13d4fb0c61d1afebe89f9d6c7c049c44 · protocol 2025-06-18 |
| First / last listed | 2026-10-31 01:57 UTC / 2026-10-31 01:57 UTC |
| Grade over time | 2026-10-31: F (39), 34 tools |
Is this your server? Own a server? ToolFit hosted watch re-checks it every 24 h ($0.25 per 30 days) or 6 h ($0.60) and sends you an HMAC-signed webhook when its tools or grade change: POST https://api.youraitools.co/toolfit/v1/watch. To opt out, see About & opt-out.
Tools: search_companies get_company_details get_job_details update_job_application_status toggle_job_application_interest get_recent_applications search_job_applications get_job_application create_job_application find_job_application update_job_application lookup_h1b_sponsorship check_stale_applications weekly_job_search_summary get_job_fit_evidence prepare_for_interview add_career_entry update_career_entry list_career_entries delete_career_entry get_career_journal_prompts list_experiences add_job_application_note list_job_application_notes update_job_application_note delete_job_application_note search_contacts get_contact update_contact_status add_contact_interaction get_career_compass generate_career_compass save_career_compass recommend_target_roles
search_companies | Search for companies by name to retrieve their unique identifiers (UUIDs). params: name* |
get_company_details | Get detailed information about a company (applicants by status, Community Signal, H1B sponsorship status, employee count, website, etc.) using its UUID.
The metrics window defaults to the last 30 days. Optional startDate and endDate parameters support other date ranges. Returns GigHQ's recorded company data and community metrics for the selected window. params: companyId*, startDate, endDate |
get_job_details | Get detailed community metrics for a specific job listing (applicants by status, average days per status, Community Signal) using its UUID.
The metrics window defaults to the last 30 days. When the user requests a longer period — e.g. "last 6 months", "last year", "since January" — compute startDate and endDate from that phrase and pass them explicitly. params: jobId*, startDate, endDate |
update_job_application_status | STOP — if the user says "not interested", "no longer interested", "withdraw interest", "remove from pipeline", or any equivalent: do NOT call this tool. Call toggle_job_application_interest instead. There is no "not interested" status here; attempting to use REJECTED or any other status as a proxy is wrong.
Updates the status of a job application by its UUID to one of the supported pipeline stage params: uuid*, currentStatus*, status* |
toggle_job_application_interest | Use this tool when the user says "not interested", "no longer interested", "withdraw interest", "I'm out", "remove from pipeline", or any equivalent phrase. This is the ONLY correct tool for withdrawing interest — do not use update_job_application_status as a proxy.
Deactivates an active application (or reactivates a previously deactivated one). Mirrors the "I am no longer interested in this role params: uuid*, currentIsActive* |
get_recent_applications | Retrieves a summary of the user's 10 most recent job applications, including status, company name, and correspondence dates. `totalCount` in the response reflects the full number of applications, not just the 10 returned — mention it if it's larger than the list shown, and point the user to search_job_applications for the rest. params: none |
search_job_applications | Search the user's job applications by company name, status, or both. Use this when the user asks about a specific company's application, wants to find a particular application to view or update its status, or wants to know how many applications are in a given status (e.g. "how many applications are in Prospecting?").
Omit `company` to search across all companies — required when the request is sta params: company, status, isActive, take, skip |
get_job_application | Fetches the full details of a single job application by its UUID — status history, correspondence dates, job description, and related metadata.
Do NOT use this tool when the user asks about notes ("do I have any notes", "show me my notes", "list notes"). Use list_job_application_notes for that.
Tip: if you only have a company name, call search_job_applications first to get the UUID. params: uuid* |
create_job_application | Creates a new job application entry in GigHQ, or reuses an existing active one for the same company+job if the backend finds one — check `alreadyExist` in the response. Calling find_job_application first is still recommended when you want to inspect a possible match before deciding.
New applications always start in PROSPECTING status — there is no way to create directly into APPLIED/INTERVIEWING/ params: company*, job*, source_url, job_description |
find_job_application | Checks whether the user already has a saved job application for a SPECIFIC posting — call this before create_job_application to avoid creating a duplicate. Matches BOTH company name and job title (case-insensitive substring on each), so it can tell two different roles at the same company apart. search_job_applications cannot do this — it only filters by company/status/isActive, not job title.
Bot params: company*, job* |
update_job_application | Enriches or corrects an existing job application's saved posting details: source URL and/or job description. Use this when the user finds the JD later, wants to add the posting link, or wants to correct the saved description.
Do NOT use this for status changes — use update_job_application_status. Do NOT use this for withdraw/reactivate ('not interested') — use toggle_job_application_interest. Thi params: uuid*, source_url, job_description |
lookup_h1b_sponsorship | Looks up a company by name and returns GigHQ's recorded H1B sponsorship and concurrent H1B flags. Returns unknown when a flag is unavailable. These results describe the data recorded in GigHQ. params: company_name* |
check_stale_applications | Returns job applications that haven't had a status update in a configurable number of days, along with a suggested follow-up action for each. Useful for surfacing applications the user may have forgotten about. params: days |
weekly_job_search_summary | Generates a weekly job search health summary. Aggregates up to 30 active applications and surfaces status distribution, conversion rates, longest-open applications, pipeline clustering insights, and a suggested focus area for the coming week. params: none |
get_job_fit_evidence | Retrieves a saved GigHQ job application, candidate profile data, and the most relevant Career Journal evidence for assessing role fit. Career evidence is ranked by job keywords, competency coverage, evidence quality, recency, and diversity; the default is 20 entries, grouped by competency bucket (career_journal.competency_rollup) to make coverage and gaps easy to spot. This read-only tool supplies params: application_uuid*, career_entry_limit |
prepare_for_interview | Assembles everything needed to prepare for an interview on a saved GigHQ job application: the job and company context, the candidate's full profile, their Career Journal grouped by role (for STAR/CAR story material), which evidence best matches the role (to emphasize) and which competencies are weakly covered (to address or reframe), and a company briefing (Community Signal, H1B status, size). Thi params: application_uuid* |
add_career_entry | Saves a new career journal entry to the user's GigHQ profile. Use this to document professional achievements, projects, skills acquired, or reflections tied to a specific role.
Entry types:
1 = achievement — a concrete win, result, or impact (default)
2 = project — a specific initiative the user owned or contributed to
3 = skill_acquired — a new skill, tool, or capability gained
4 = refle params: title*, description*, type, experience_id, entry_date, metrics, tags |
update_career_entry | Updates an existing career journal entry. Only the fields provided will be changed — all other fields remain as-is. Use this to refine descriptions, add missing numbers to the metrics field, correct the entry date, or re-type an entry. This is the right tool to backfill quantification on entries saved without a full three-number breakdown (scale of action, direct result, organizational impact). params: uuid*, title, description, type, experience_id, entry_date, metrics, tags |
list_career_entries | Returns the user's career journal entries from GigHQ, newest first. Supports optional filtering by entry type and date range.
Use this tool to:
- Review what the user has already documented before starting a journaling session
- Find entries to update or refine
- Identify gaps (roles with few or no entries)
- Synthesise entries into resume bullets or interview stories
Entry type filter v params: type, start_date, end_date, take, skip |
delete_career_entry | Permanently deletes a career journal entry by UUID. This action cannot be undone — confirm with the user before calling. Use list_career_entries to find the UUID if you don't have it. params: uuid* |
get_career_journal_prompts | Returns a set of context-aware reflection questions to guide a career journaling session. Use this at the start of any journaling conversation to orient the discussion.
The tool reads the user's GigHQ experience records and existing career entries to tailor the questions — surfacing the most relevant role, estimating tenure, and flagging roles with sparse documentation.
Session types:
achievem params: session_type |
list_experiences | Returns the user's work experience records with their integer IDs.
Use this tool BEFORE calling `add_career_entry` or `update_career_entry` to find the
correct `experience_id` for the role the entry belongs to. Present the role list to
the user and confirm which one they mean before saving.
This is the tool-based alternative to the `gighq://experience` resource and works in
all contexts includin params: none |
add_job_application_note | Adds a note to a job application's timeline. Use this to log any touchpoint or interaction — a call, a LinkedIn message, a referral conversation, a networking event, etc.
**category is required.** Infer the best-fit category from the note content before calling. Use this mapping:
• text_message — contact via SMS/text
• email_external — contact via email
• call — phone or video call
• link params: application_id*, body*, category* |
list_job_application_notes | Use this tool when the user asks about notes on a job application — "do I have any notes", "show me my notes", "what notes do I have", etc. Returns all user-authored notes for a job application ordered by date, including UUID, body text, category, and timestamp. Use the returned UUIDs in follow-up update_job_application_note or delete_job_application_note calls. params: application_id* |
update_job_application_note | Updates the body or category of an existing job application note. Both body and category are required — the backend replaces the full note on update.
If the user only mentions updating the body and doesn't specify a category, infer the best-fit category from the note content using this mapping:
• text_message — contact via SMS/text
• email_external — contact via email
• call — phone or vide params: note_uuid*, application_id*, body*, category* |
delete_job_application_note | Permanently deletes a note from a job application's timeline. This action cannot be undone — confirm with the user before calling. Use list_job_application_notes to find the note UUID if you don't have it. params: note_uuid*, application_id* |
search_contacts | Searches the user's job-search contacts in GigHQ — recruiters, hiring managers, referrals, and other people they are networking with.
Use this tool to:
- Find a contact before drafting an outreach or follow-up message
- See who the user already knows at a company before an interview or application
- Review which contacts are stuck at a given outreach stage
Status filter values: not_contact params: name, status, take, skip |
get_contact | Returns full details for one of the user's job-search contacts: profile info, outreach status, linked job applications, and the complete interaction history (calls, LinkedIn messages, coffee chats, etc.).
Use this before drafting outreach or follow-up messages so the message reflects what has already been said, and before interviews to remind the user who they know at the company.
Find the UUID w params: contact_id* |
update_contact_status | Updates a contact's outreach status in GigHQ. A status-change entry is automatically logged in the contact's interaction history.
Status progression: not_contacted → reached_out → responded → in_conversation → connected. Use 'cold' when the thread has gone quiet.
Find the contact's UUID with `search_contacts`. params: contact_id*, status* |
add_contact_interaction | Logs a touchpoint with one of the user's job-search contacts — a call, a LinkedIn message, a coffee chat, a referral conversation, etc. The entry appears in the contact's interaction timeline in GigHQ.
**type is required.** Infer the best-fit type from what happened:
• text_message — SMS/text
• email_external — email
• call — phone or video call
• linkedin_connection_request — sent or acc params: contact_id*, type*, body*, occurred_at |
get_career_compass | Retrieves the user's saved CareerCompass data: professional objectives, positioning statement, categorized skills (technical/soft/management/other), and target market (industries, company size, geographic location). Cheap read — prefer this over generate_career_compass whenever the user just wants to review what's already saved. params: none |
generate_career_compass | Runs GigHQ's CareerCompass AI pipeline against the user's resume data to generate 3 candidate professional objective statements, a positioning statement, categorized skills, and a suggested target market (industries, company sizes, geographic locations). This is an EXPENSIVE, one-time 'career strategy' action (4 parallel AI completions server-side) — not a cheap or repeatable lookup. Prefer get_ca params: career_stage, career_switch_details |
save_career_compass | Persists CareerCompass data to the user's GigHQ profile. This REPLACES the full saved record — any array field you omit (technical_skills, soft_skills, management_skills, target_industries, company_size, geographic_location, other_skills) is saved as empty, not left unchanged. Call get_career_compass first and pass through every field the user isn't changing. Only call this after the user has revi params: professional_objectives, positioning_statement, technical_skills, soft_skills, management_skills, other_skills, target_industries, company_size, geographic_location, career_stage, career_switch_type, target_industry, target_role, is_complete, progress_step, objective_suggestions, target_job_titles |
recommend_target_roles | Assembles the user's profile, experience, career journal evidence (with a broad competency rollup), and saved CareerCompass data (if any) for recommending role titles to target. This is the inverse of get_job_fit_evidence: instead of evaluating fit for one specific job, it starts from the candidate's profile. Role taxonomy only — it does NOT validate recommendations against live job-market demand params: industry_preference, seniority, open_to_pivot, location_preference |
Entries describe changes in tool definitions. They are not statements about a server, its quality or its author. The grade measures how the tool definitions fit model providers (token cost, schema compatibility, confusable names) as scored by the ToolFit engine at the time of the listing. JSON: append .json. Opt-out: how or hello@youraitools.co.