Skip to main content
Glama
HireLayer MCP server

HireLayer MCP server

Resume Parser

parse_resume

Converts a resume or CV file, URL, or text into structured JSON containing contact details, work experience, education, skills, languages, and full text for applicant tracking and candidate screening.

Instructions

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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "parse_resume"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_urlNoPublic URL of a resume file to download.
file_pathNoAbsolute path of a local resume file.
workspaceNoThe client company this call belongs to, when the user recruits for several companies: its HireLayer workspace id (letters, digits and . _ : ~ -, up to 200 characters), e.g. acme-corp. Jobs, resumes and scores stay apart from other clients'. A new id creates a new workspace, so reuse the exact id. Omit it for the user's default workspace.
resume_textNoResume as plain text, when no file is available.
application_idNoYour id for this resume, such as the application or candidate id of your ATS (letters, digits and . _ : ~ -, up to 200 characters). The resume is stored under it, replacing a resume stored under the same id. Omit it when you have no such id: the resume is stored under an id drawn from the file.
do_not_store_dataNotrue: HireLayer keeps nothing of this parse and application_id comes back null. Enterprise plan only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv2.1.0
    • changedInput schema / properties / application_id / description
      Previous value: -"Your own reference, echoed back in the result."New value: +"Your id for this resume, such as the application or candidate id of your ATS (letters, digits and . _ : ~ -, up to 200 characters). The resume is stored under it, replacing a resume stored under the same id. Omit it when you have no such id: the resume is stored under an id drawn from the file."
    • addedInput schema / properties / application_id / pattern
      Added value: +"^[A-Za-z0-9._:~-]{1,200}$"
    • changedInput schema / properties / do_not_store_data / description
      Previous value: -"true: HireLayer does not keep the file after parsing."New value: +"true: HireLayer keeps nothing of this parse and application_id comes back null. Enterprise plan only."
    • addedInput schema / properties / resume_text
      Added value: +{
      +  "description": "Resume as plain text, when no file is available.",
      +  "maxLength": 100000,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / workspace
      Added value: +{
      +  "description": "The client company this call belongs to, when the user recruits for several companies: its HireLayer workspace id (letters, digits and . _ : ~ -, up to 200 characters), e.g. acme-corp. Jobs, resumes and scores stay apart from other clients'. A new id creates a new workspace, so reuse the exact id. Omit it for the user's default workspace.",
      +  "pattern": "^[A-Za-z0-9._:~-]{1,200}$",
      +  "type": "string"
      +}
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With annotations already indicating non-read-only and open-world behavior, the description adds critical side-effect details: HireLayer stores the resume under application_id, replaces a resume stored under the same id, and supports do_not_store_data. It also discloses runtime (~30 seconds) and credit cost, which are exactly the behavioral facts an agent needs before invoking this parser.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded and every sentence carries useful information, including formats, inputs, storage, latency, and cost. However, it is a dense single paragraph with a long format list and output-field list, making it less scannable than ideal.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description compensates by naming the structured output sections and the full resume text path. It also covers accepted input sources, file size limits, storage behavior, privacy opt-out, runtime, and credit cost, making it complete enough to invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds meaningful cross-parameter semantics by requiring exactly one of file_path, file_url, or resume_text, and by explaining how application_id and do_not_store_data affect storage, going beyond the schema text.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource: parse a resume/CV into structured JSON, then names the extracted sections and full-text path. The format list and output fields make its role unmistakable versus siblings like score_resumes, search_resumes, or extract_job_criteria.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear input-selection guidance ('Give exactly one input') and explains storage/cost context, but it never states when to choose parse_resume over sibling tools such as score_resumes or search_resumes. Usage is implied by the tool purpose rather than explicitly guided against alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.