Civify

Parse Resume Document

civify_parse_cv

Read-onlyIdempotent

Parse a resume document (PDF, DOCX, image) into structured JSON schema containing contact details, work experience, education, skills, and projects.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`api_key`	No	Optional API key override.
`filename`	No	Filename when providing base64 (e.g., 'resume.pdf').	resume.pdf
`language`	No	Language code (e.g. 'en', 'ar', 'auto'). Default is 'auto'.	auto
`file_base64`	No	Base64 encoded content of the resume document (PDF, DOCX). Recommended for remote/cloud MCP servers.
`resume_text`	No	Plain text or markdown content of the resume. Easiest option when chatting with an AI agent.
`server_file_path`	No	Local file path on the MCP server machine. For local CLI/stdio usage only. In ChatGPT or Claude, pass 'resume_text' or 'file_base64' instead.

Output Schema

TableJSON Schema

Name	Required	Description
`skills`	No	Technical and domain skills extracted
`contact`	No	Candidate contact information (name, email, phone, location, links)
`message`	No	Diagnostic or status message
`success`	No	Whether the document was successfully parsed
`summary`	No	Professional summary statement
`projects`	No	Key projects and achievements
`education`	No	Academic degrees and certifications
`experience`	No	Chronological employment history
`resumeData`	No	Parsed resume sections including contact, experience, education, skills, and projects
`detectedLanguage`	No	Primary detected language code (e.g., 'en', 'ar')

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 15, 2026

changedInput schema / anyOf

Previous value: -[
-  {
-    "required": [
-      "resume_text"
-    ]
-  },
-  {
-    "required": [
-      "file_base64"
-    ]
-  },
-  {
-    "required": [
-      "file_path"
-    ]
-  }
-]New value: +[
+  {
+    "required": [
+      "resume_text"
+    ]
+  },
+  {
+    "required": [
+      "file_base64"
+    ]
+  },
+  {
+    "required": [
+      "server_file_path"
+    ]
+  }
+]

removedInput schema / properties / file_path

Removed value: -{
-  "description": "Local file path on the MCP server machine. Do NOT use for remote cloud servers; use 'resume_text' or 'file_base64' instead.",
-  "type": "string"
-}

addedInput schema / properties / server_file_path

Added value: +{
+  "description": "Local file path on the MCP server machine. For local CLI/stdio usage only. In ChatGPT or Claude, pass 'resume_text' or 'file_base64' instead.",
+  "type": "string"
+}

First observedSep 15, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already cover the safety profile via readOnlyHint, idempotentHint, and destructiveHint. The description adds accepted document types and output contents, but it does not explain failure modes, authentication needs, or the 'image' input claim that is not reflected in the schema.

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

Conciseness5/5

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

The description is a single, front-loaded sentence with no filler. It conveys the action, resource, input formats, and output content efficiently.

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

Completeness4/5

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

Given the rich input schema and the presence of an output schema, the description is largely complete for a parse operation. It falls slightly short by not addressing the image-input discrepancy or clarifying where this tool fits relative to the CV workflow siblings.

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

Parameters3/5

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

Schema description coverage is 100%, so each parameter is already documented. The description adds no parameter-level meaning and even mentions 'image' support, while the schema's file_base64 parameter only describes PDF/DOCX.

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 states a specific verb ('Parse') and resource ('resume document') and enumerates the output fields (contact details, work experience, education, skills, projects). This clearly distinguishes it from siblings like civify_score_ats or civify_mask_pii.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives such as civify_score_ats, civify_tailor_cv, or civify_mask_pii. The description only defines what the tool does, leaving the agent to infer the appropriate context.

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

All Civify tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?