Skip to main content
Glama
rajeshaipython-stack

ResumePilot MCP

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
upload_master_resumeA

Register the user's ONE master resume (PDF, DOCX, TXT, or Markdown). Provide either a local file path (preferred — the file is on the user's machine) or raw text. The original is stored immutably and never modified.

analyze_master_resumeA

Parse the stored master resume into structured professional information, build a draft Master Profile, and return the list of missing fields ResumePilot should ask the user about. Nothing is invented.

setup_user_profileA

Apply the user's answers to the missing-information questionnaire, merging them into the Master Profile. Pass an answers object keyed by field name (e.g. { fullName, email, phone, location, workAuthorization, workModePreference, noticePeriod, salaryExpectation, preferredRoles }). Only fills provided fields; never overwrites with blanks; never asks twice.

get_user_profileB

Return the current Master Profile and any still-missing fields.

update_user_profileA

Update specific Master Profile fields with an updates object. Same merge semantics as setup_user_profile. Use for corrections or adding preferences (e.g. preferredLocations, relocationPreference, reusable application answers).

connect_job_sourceA

Inspect or connect a job source adapter (professional networks, global/regional job boards, company career pages, public job APIs, supported ATS pages). Phase 1 has the manual source ready. Real search adapters connect via their OFFICIAL login/OAuth in later phases — ResumePilot never stores passwords or OTPs.

search_jobsB

Search connected job sources for relevant jobs (up to JOB_SEARCH_MAX_JOBS with JOB_SEARCH_CONCURRENCY workers). In Phase 1 no automated search source is connected yet — paste a job description into analyze_job instead. This tool returns the planned configuration and which sources could serve the query.

analyze_jobA

Ingest a job (Phase 1: paste the description) and analyze it against the master resume + profile. Extracts structured job info, computes the ORIGINAL ATS/match scores, and identifies missing keywords, buried experience, weak bullets and unverifiable requirements (never invented). Creates a tracked application and returns its number. Follow with optimize_resume_for_job.

rank_jobsA

Rank all analyzed applications by overall match score (ATS as tiebreaker) and flag which clear the MATCH_SCORE_THRESHOLD for applying.

optimize_resume_for_jobA

Generate a job-specific tailored resume for a tracked application. Surfaces already-demonstrated keywords, reorders skills/bullets, and adds a role-targeted summary — using ONLY information genuinely present in the master resume/profile. Never invents skills, experience, education or certifications. Produces PDF + DOCX and returns original vs optimized ATS scores, the changes made, and any requirements that could not be verified.

generate_application_profileA

Build the job-specific application profile: the reusable fields ResumePilot can safely autofill from the VERIFIED master profile, the known answers, and the questions that must be answered by the user (never guessed — especially legal/declaration answers).

prepare_applicationA

Prepare everything needed to apply: autofill map, customized resume to attach, and a step-by-step manual checklist. In Phase 1 nothing is auto-submitted to external sites — the application is set to READY_TO_APPLY and any human-only steps (login, CAPTCHA, OTP, 2FA, identity, legal declarations) are listed for the user.

apply_to_jobA

Attempt to submit the application through the resolved application adapter. In Phase 1 the manual adapter never auto-submits to external sites: it returns PAUSED_FOR_USER with a checklist. Pass markApplied: true ONLY after the user confirms they submitted it themselves, to record it as APPLIED.

get_application_statusB

Return the status, scores and timeline of one application (by number) or all applications.

search_application_emailsB

Search the connected email provider for messages related to an application (by company, role, recruiter email, or domain), classify each into a status (APPLICATION_RECEIVED, SCREENING, INTERVIEW, OFFER, REJECTED, ...), and update the application's tracking. Phase 1 uses an offline mock provider (seed it in tests/demos); Phase 5 connects Gmail via OAuth (read-only, no passwords stored).

update_application_trackingB

Manually update an application's tracking: set a new status (with timestamped history) and/or attach an email update. Use to record interviews, offers, rejections, or withdrawals.

generate_application_reportB

Generate the final professional PDF report (summary stats + application table + per-application detail sections) and the local HTML tracking pages (one per application, plus an index). Returns the file paths so the user can open/download them.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rajeshaipython-stack/auto-apply-resume-pilot'

If you have feedback or need assistance with the MCP directory API, please join our Discord server