Resume Data Extraction
extract_resume_dataExtracts structured data from a resume or CV supplied as plain text or a Base64-encoded document. Returns candidate information such as contact details, skills, work experience, education, certifications, and taxonomy-enriched data for AI recruiting workflows. Supports multiple languages with English-normalized output.
Use this tool when a user asks to extract resume data, read candidate details, identify skills and employment history, or convert resume content into structured information for recruiting workflows.
Provide either resume_text containing the complete, verbatim resume text, or resume_base64 containing a Base64-encoded document, but not both. When using resume_base64, include the original filename and extension. For a resume available at a public URL, use extract_resume_data_from_url instead.
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": "extract_resume_data"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| filename | No | Optional for resume_text (default 'inline_resume.txt'). Required for resume_base64 and must include the original file extension. | |
| resume_text | No | Complete, verbatim plain-text of the resume/CV — every line exactly as in the original. Do NOT summarise, paraphrase, or base64-encode; pass raw text. | |
| resume_base64 | No | Raw Base64-encoded resume file content (PDF, DOC, DOCX, RTF, TXT). Provide the original filename. Use either resume_text or resume_base64, not both. Do not include a data URI prefix. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| data | Yes | Tool-specific result payload. The exact fields depend on which tool produced this result. | |
| meta | Yes | Request metadata: unique trace ID and server-side processing latency. | |
| success | No | Always ``true`` for a successful result. Check this field first to distinguish success from error envelopes. |