HireLayer MCP server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HIRELAYER_API_KEY | Yes | Your HireLayer API key, copied from your dashboard after creating an account at hirelayer.co. | |
| HIRELAYER_BASE_URL | No | The base URL for the HireLayer API. | https://hirelayer.co |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| parse_resumeA | Parse a resume / CV (PDF, DOC, DOCX, ODT, PPT, PPTX, ODP, XLS, RTF, TXT, HTML, Markdown, JPG, PNG or BMP, under 4.5 MB) into structured JSON, in resume: contact details, work experience, education, languages, skills and the full resume text in resume.info_resume.text. Give exactly one input: file_path (a local file), file_url (a public URL) or resume_text. HireLayer keeps the resume in the user's resume database under application_id, unless do_not_store_data is set. Takes about 30 seconds. Costs 1 HireLayer credit, 0 for a file already stored. |
| extract_job_criteriaA | Turn a job description (any language, at least 30 characters) into the typed criteria it states (usually 4 to 10, fewer for a short posting), in the posting's order, each with a criterion_id, a label, a type, a requirement (required, preferred or bonus), a weight from 0 to 3 and an optional threshold. They are written in the job's language (English, French, German, Spanish or Portuguese; English for any other) unless language says otherwise. The job is stored under job_id, so score_resumes can reuse it. Free, except a new text sent under the job_id of a job already scored: its scores are evaluated again, 1 credit each. |
| score_resumesA | Evaluate 1 to 50 resumes against a job, criterion by criterion, and return them best first: for each, a score between 0 and 1, a verdict (highly_relevant, relevant, marginally_relevant or not_relevant), a summary, the required criteria missing or to verify, and the evidence for each criterion. Give the job as job_text (its criteria are extracted on the way, or pass your own criteria) or as the job_id of a stored job. Give each resume as text or as the application_id of a stored resume; at least one resume of the call holds 30 characters or more. Summaries and explanations are written in the job's language. With precise_ranking, the 10 best are re-ranked against each other, each with a ranking_reason. The result is decision support for a human recruiter, not an automated hiring decision. Costs 1 HireLayer credit per resume evaluated, and 1 more with precise_ranking; a pair already scored costs 0. |
| search_resumesA | Find the resumes of the user's resume database closest to a job, by proximity only: application_ids with a similarity between 0 and 1, best first, and whether each is already scored for the job. No evaluation: pass the ones worth it to score_resumes. Give the job as the job_id of a stored job or as job_text (at least 30 characters; the job is then stored). Costs 1 HireLayer credit per search. |
| search_jobsA | Find the user's stored open jobs closest to a resume, by proximity only: job_ids with their title and a similarity between 0 and 1, best first, and whether the resume is already scored for each. No evaluation: score the ones worth it with score_resumes. Give the resume as the application_id of a stored resume or as resume_text (the resume is then stored). Costs 1 HireLayer credit per search. |
| normalize_skillsA | Map free-text skills (one skill, a compound string or a whole skills section) to skills of the HireLayer taxonomy, with their IDs, families and domains, named in French or English. Unmatched parts are listed in unresolved. Costs 1 HireLayer credit. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| screen_candidates | Score each candidate against a job description and build a shortlist. |
| summarize_resume | Parse one resume and write a short recruiter-style candidate summary. |
| normalize_skills_list | Map a free-text skills section to standard taxonomy skills. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a recognizably different role: parsing, criteria extraction, evaluation scoring, two proximity searches, and skill normalization. The main potential confusion is between search_resumes/search_jobs (proximity only) and score_resumes (evaluation), but the descriptions explicitly contrast 'no evaluation' versus scoring, which resolves most ambiguity.
All six tools follow a strict snake_case verb_noun pattern (parse_resume, extract_job_criteria, score_resumes, search_resumes, search_jobs, normalize_skills). The verb accurately reflects the action in every case with no mixed conventions.
Six tools is well within the ideal 3-15 range and each maps to a distinct stage of the recruiting workflow (parse, extract, search, score, normalize). No tool feels redundant or trivially thin.
The surface covers the full resume-to-job matching pipeline: parsing, criteria extraction, bidirectional search, scoring, and skill normalization. Minor gaps exist around managing stored artifacts (e.g., listing or deleting stored resumes/jobs by application_id/job_id), but core workflows have no dead ends.