Skip to main content
Glama

Server Details

Job-search tracker for AI agents: applications, stale follow-ups, skills gaps, H-1B lookup.

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
OAuth
Works in Glama
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
gighq-ai/gighq-skill
GitHub Stars
0
ChatGPT
–
Claude
–

TDQS

A3.9/5.0

Scored across 34 tools

Disambiguation4/5

Most tools map to a distinct resource/action pair, and descriptions carefully differentiate close pairs such as find_job_application vs search_job_applications, update_job_application_status vs toggle_job_application_interest, and get_career_compass vs generate_career_compass. Some overlap remains between add_contact_interaction and add_job_application_note (both log touchpoints using the same taxonomy), and among get_job_fit_evidence, prepare_for_interview, and recommend_target_roles (all assemble context), so occasional misselection is possible.

Naming Consistency5/5

All tool names use snake_case and follow a verb-first pattern (add_, get_, list_, search_, update_, delete_, toggle_, etc.) with predictable noun phrases. Minor variation like get_recent_applications is still consistent with the overall convention.

Tool Count2/5

At 34 tools, the surface is well above the typical 3-15 well-scoped range and falls into the 'too many' band. While the domain is broad (applications, contacts, companies, career journal, career strategy), several retrieval and context-assembly tools could be consolidated to reduce cognitive load.

Completeness4/5

Core lifecycle coverage is strong: career journal CRUD, job application CRUD plus status/interest/notes, contact lookup and interactions, company/job metrics, and career strategy tools. Minor gaps exist—there is no delete_job_application, and contacts cannot be created or deleted via this MCP (explicitly by design)—but agents can generally work around them.

Available Tools

34 tools
add_career_entryAInspect

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 = reflection — a lesson learned or professional observation

Tip: if the user hasn't specified a role, call list_experiences first, present the options, and ask which role this entry belongs to. Then pass the confirmed integer ID as experience_id. experience_id is optional — entries without one are valid but less useful for resume generation and interview prep, since they can't be linked to a specific role.

STAR structure (achievement entries): walk the user through their story in order, one piece at a time — don't interrogate with a checklist — Situation: the context or challenge beforehand Task: what specifically needed to be done or the goal to achieve Action: the concrete steps actually taken Result: the outcome, ideally with (1) scale of action: how much, how many, what scope (team size, users, codebase size, budget, requests/sec, etc.), (2) direct result: the measurable outcome (latency reduced by X%, errors down by Y, shipped Z weeks ahead of schedule), and (3) organizational impact: what that result meant for the business, team, or users (saved $X, unblocked N engineers, contributed to Y% revenue growth) Write description as a clearly labeled STAR narrative — "Situation: ... Task: ... Action: ... Result: ..." — rather than one unstructured paragraph. Before calling this tool for an achievement entry, confirm you have all four STAR parts from the user. If the Result's numbers are genuinely unavailable, note that in the description and ask the user to follow up later via update_career_entry. Project entries benefit from the same Result-quantification numbers but don't need the full STAR narrative structure. Put the quantified numbers from Result in the metrics field as well — not buried only in the description.

Inputs: title (required), context (required), description (required), tags, +6 more. Returns: uuid, entry, message, profileUrl, +1 more

add_contact_interactionAInspect

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 accepted a connection request • linkedin_message — direct message on LinkedIn • coffee_chat — informational interview or coffee chat • in_person_meeting — face-to-face meeting • networking_event — conference, meetup, career fair • referral — the contact referred the user or made an introduction • other — anything else

Find the contact's UUID with search_contacts.

Inputs: body (required), type (required), context (required), contact_id (required), +3 more. Returns: uuid, message, contactUrl

add_job_application_noteAInspect

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 • linkedin_connection_request — sent or received a LinkedIn connection request • linkedin_message — direct message on LinkedIn • coffee_chat — informational interview or coffee chat • in_person_meeting — face-to-face meeting • networking_event — conference, meetup, career fair, or similar event • referral — someone referred the user or made an introduction • other — genuinely doesn't fit any of the above

If the category is still ambiguous after reading the note, present the options to the user and ask them to confirm before calling this tool. The application_id is the UUID of the job application — use get_recent_applications or search_job_applications to find it.

Inputs: body (required), context (required), category (required), application_id (required), +2 more. Returns: uuid, appUrl, message

check_stale_applicationsA
Read-only
Inspect

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.

Inputs: context (required), days, llm_model, conversation_id. Returns: staleCount, applications, dashboardUrl, thresholdDays

create_job_applicationA
Destructive
Inspect

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/etc. If the user has already applied, call update_job_application_status with status "APPLIED" right after this returns.

Optionally pass source_url and/or job_description to save them in the same call — attached best-effort after the application is created/found. If that secondary save fails, the create/find itself still succeeds and a warning is included in the response instead of an error. When an existing application is reused, supplied posting details can replace its saved source URL or job description.

Inputs: job (required), company (required), context (required), llm_model, +3 more. Returns: uuid, appUrl, warnings, application, +1 more

delete_career_entryA
Destructive
Inspect

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.

Inputs: uuid (required), context (required), llm_model, conversation_id. Returns: uuid, entry, message, profileUrl, +1 more

delete_job_application_noteA
Destructive
Inspect

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.

Inputs: context (required), note_uuid (required), application_id (required), llm_model, +1 more. Returns: uuid, appUrl, message

find_job_applicationA
Read-only
Inspect

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.

Both company and job are required.

Scope limitation: matches are restricted server-side to APPLIED, INTERVIEWING, and PROSPECTING status. An application the user marked REJECTED/OFFER, or withdrew interest in, will NOT appear here even if the title/company match.

If found is false, it's safe to call create_job_application. If true, prefer reusing the existing UUID (e.g. via update_job_application or add_job_application_note) instead of creating a duplicate.

Inputs: job (required), company (required), context (required), llm_model, +1 more. Returns: count, found, matches

generate_career_compassA
Read-only
Inspect

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_career_compass first to check for existing saved data. Nothing is persisted by this call; use save_career_compass afterward, and only with the user's explicit review and authorization.

Inputs: context (required), llm_model, career_stage, conversation_id, +1 more. Returns: skills, purpose, objectives, target_market, +2 more

get_career_compassA
Read-only
Inspect

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.

Inputs: context (required), llm_model, conversation_id. Returns: is_saved, soft_skills, target_role, career_stage, +12 more

get_career_journal_promptsA
Read-only
Inspect

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: achievement — document a specific win or impact quarterly — end-of-quarter reflection (default) onboarding — first 90 days at a new role wrap-up — leaving a role or wrapping up an internship job-search — actively applying; synthesise story and close gaps

Inputs: context (required), llm_model, session_type, conversation_id. Returns: gap_note, instruction, profile_url, session_type, +3 more

get_company_detailsA
Read-only
Inspect

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.

Inputs: context (required), companyId (required), endDate, llm_model, +2 more. Returns: data

get_contactA
Read-only
Inspect

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 with search_contacts.

Inputs: context (required), contact_id (required), llm_model, conversation_id. Returns: contact, contactUrl

get_job_applicationA
Read-only
Inspect

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.

Inputs: uuid (required), context (required), llm_model, conversation_id. Returns: appUrl, aiSummary, application

get_job_detailsA
Read-only
Inspect

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.

Inputs: jobId (required), context (required), endDate, llm_model, +2 more. Returns: data

get_job_fit_evidenceA
Read-only
Inspect

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 evidence and retrieval metadata only. It does not assess the candidate, calculate a fit score, or modify records. If the job description is missing, it returns the application link and a substantive/recent evidence fallback.

Inputs: context (required), application_uuid (required), llm_model, conversation_id, +1 more. Returns: purpose, candidate, provenance, application, +3 more

get_recent_applicationsA
Read-only
Inspect

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.

Inputs: context (required), llm_model, conversation_id. Returns: tips, totalCount, applications, dashboardUrl, +1 more

list_career_entriesA
Read-only
Inspect

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 values: 1=achievement, 2=project, 3=skill_acquired, 4=reflection.

Inputs: context (required), skip, take, type, +4 more. Returns: total, entries, returned, profileUrl

list_experiencesA
Read-only
Inspect

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 including voice mode.

Inputs: context (required), llm_model, conversation_id. Returns: experiences

list_job_application_notesA
Read-only
Inspect

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.

Inputs: context (required), application_id (required), llm_model, conversation_id. Returns: count, notes, appUrl, application_id

lookup_h1b_sponsorshipA
Read-only
Inspect

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.

Inputs: context (required), company_name (required), llm_model, conversation_id. Returns: uuid, company, h1b_sponsor, supports_h1b_transfers

prepare_for_interviewA
Read-only
Inspect

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). This read-only tool supplies context only — it does not generate interview questions, write STAR/CAR answers, or assess the candidate.

Inputs: context (required), application_uuid (required), llm_model, conversation_id. Returns: purpose, candidate, fit_signal, provenance, +5 more

recommend_target_rolesA
Read-only
Inspect

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 or hiring volume; that is future work. This read-only tool assembles context only; the client model produces the tiered (Strong fit / Stretch / Not recommended) recommendation.

Inputs: context (required), llm_model, seniority, open_to_pivot, +3 more. Returns: purpose, candidate, provenance, career_compass, +2 more

save_career_compassA
Destructive
Inspect

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 reviewed the content (e.g. from generate_career_compass) and explicitly authorized saving it.

Inputs: context (required), llm_model, is_complete, soft_skills, +16 more. Returns: message, profileUrl

search_companiesA
Read-only
Inspect

Search for companies by name to retrieve their unique identifiers (UUIDs).

Inputs: name (required), context (required), llm_model, conversation_id. Returns: count, results

search_contactsA
Read-only
Inspect

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_contacted, reached_out, responded, in_conversation, connected, cold. Contacts are created in the GigHQ app or via the browser extension — this MCP connection cannot create or delete them.

Inputs: context (required), name, skip, take, +3 more. Returns: total, contacts, returned, contactsUrl

search_job_applicationsA
Read-only
Inspect

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 status-only.

Returns matching applications with their UUIDs — the UUID is what feeds into update_job_application_status and toggle_job_application_interest. totalCount in the response reflects the full match count, not just the page returned (see take/skip).

Matching is case-insensitive and substring-based: "stripe" matches "Stripe", "Stripe Inc", etc. If the user applied to the same company more than once (e.g., different roles), all matches are returned; use jobTitle and correspondenceDate to disambiguate.

Inputs: context (required), skip, take, status, +4 more. Returns: results, totalCount

toggle_job_application_interestA
Destructive
Inspect

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" button in the GigHQ app.

Pass currentIsActive: true to deactivate an active application:

  • Stamps an end date on the current status stage (appliedEndDate, interviewingEndDate, or offerEndDate)

  • Sets status to CANDIDATE_WITHDREW and sets endDate = now

Pass currentIsActive: false to reactivate a previously deactivated application:

  • Clears endDate and resets status to APPLIED

Check the current isActive value with get_job_application or search_job_applications before calling.

Inputs: uuid (required), context (required), currentIsActive (required), llm_model, +1 more. Returns: result, message

update_career_entryA
Destructive
Inspect

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).

Inputs: uuid (required), context (required), tags, type, +7 more. Returns: uuid, entry, message, profileUrl, +1 more

update_contact_statusAInspect

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.

Inputs: status (required), context (required), contact_id (required), llm_model, +1 more. Returns: uuid, message, contactUrl

update_job_applicationA
Destructive
Inspect

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. This tool only touches source_url and job_description.

At least one of source_url or job_description is required. job_description REPLACES the previously saved description — pass the full text, not a diff. Omitting a field leaves it unchanged.

Inputs: uuid (required), context (required), llm_model, source_url, +2 more. Returns: uuid, appUrl, message, updatedFields

update_job_application_noteA
Destructive
Inspect

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 video call • linkedin_connection_request — sent or received a LinkedIn connection request • linkedin_message — direct message on LinkedIn • coffee_chat — informational interview or coffee chat • in_person_meeting — face-to-face meeting • networking_event — conference, meetup, career fair, or similar event • referral — someone referred the user or made an introduction • other — genuinely doesn't fit any of the above

If ambiguous, ask the user to confirm before calling. Use list_job_application_notes to retrieve the note UUID if you don't have it.

Inputs: body (required), context (required), category (required), note_uuid (required), +3 more. Returns: uuid, appUrl, message

update_job_application_statusAInspect

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 stages.

Status meanings:

  • REJECTED: the company rejected the candidate (recorded internally as company-rejected)

  • For candidate withdrawal use toggle_job_application_interest instead

Allowed transitions (invalid transitions are silently ignored by the API — validate before calling):

  • PROSPECTING → PROSPECTING, APPLIED, INTERVIEWING, OFFER, REJECTED, PENDING

  • APPLIED → APPLIED, PENDING, INTERVIEWING, OFFER, REJECTED

  • INTERVIEWING → INTERVIEWING, PENDING, OFFER, REJECTED

  • OFFER → OFFER, REJECTED, PENDING

  • REJECTED → REJECTED, PENDING, APPLIED

  • PENDING → APPLIED, INTERVIEWING, OFFER, REJECTED

  • UNKNOWN → (nothing — all transitions blocked)

Inputs: uuid (required), status (required), context (required), currentStatus (required), +2 more. Returns: result, message

weekly_job_search_summaryA
Read-only
Inspect

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.

Inputs: context (required), llm_model, conversation_id. Returns: summary, dashboardUrl

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to search company job boards, filter roles by location, remote status, posting date, and H-1B sponsorship history, track applications through status changes, and check employers' USCIS sponsorship records.
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      Enables tracking job applications through a pipeline, scheduling follow-ups, and summarizing job search progress via natural language.
      7
      -
    • A
      license
      A
      quality
      B
      maintenance
      Enables an AI chat app to check CVs for ATS parsing issues, compare them to job descriptions, search company Greenhouse and Lever job boards, screen postings for scam signals, and keep a private local application tracker.
      9
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables an AI agent to maintain a job-search profile and applications, read public job-board forms, draft answers and tailored résumés, track stages and notes, and keep local web pages updated live.
      17 npm
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.