100Hires - AI ATS & Recruitment Software

hires_create_candidate

Create a candidate, optionally with an application (job_id, stage_id) and resume text. Parse an attached resume yourself and pass the text via resume_text; never inline binary data.

Input Schema

TableJSON Schema

Name	Required	Description
`city`	No	Also used to resolve timezone
`email`	No	Used for deduplication
`phone`	No
`state`	No
`job_id`	No	Creates an application for this job
`country`	No	Name or ISO code
`profile`	No	Profile answers keyed by question text or question_id
`stage_id`	No	Initial stage; requires job_id
`timezone`	No	IANA, e.g. America/Los_Angeles; resolved from city and country if omitted
`last_name`	No
`company_id`	No
`first_name`	No
`resume_text`	No	Plain text extracted from the resume; stored as a text/plain attachment. No binary or base64.

Schema Changelog

Changes observed during successful MCP inspections.

Changed16 schema fields changedSep 9, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

removedInput schema / additionalProperties
```
Removed value: -false
```

changedInput schema / properties / city / description

Previous value: -"Candidate city for location/timezone resolution."New value: +"Also used to resolve timezone"

removedInput schema / properties / company_id / description

Removed value: -"Target company ID. Required only when the API key has access to multiple companies."

changedInput schema / properties / country / description

Previous value: -"Candidate country name or ISO code."New value: +"Name or ISO code"

changedInput schema / properties / email / description

Previous value: -"Candidate email address. Used for deduplication."New value: +"Used for deduplication"

removedInput schema / properties / first_name / description
```
Removed value: -"Candidate first name."
```

changedInput schema / properties / job_id / description

Previous value: -"Job ID to create an application for this candidate."New value: +"Creates an application for this job"

removedInput schema / properties / last_name / description
```
Removed value: -"Candidate last name."
```
removedInput schema / properties / phone / description
```
Removed value: -"Candidate phone number."
```
removedInput schema / properties / profile / additionalProperties
```
Removed value: -{
-  "type": "string"
-}
```

changedInput schema / properties / profile / description

Previous value: -"Key-value map of profile field answers. Keys can be question text or question_id. Example: {\"Current job title\": \"Senior Engineer\"}."New value: +"Profile answers keyed by question text or question_id"

changedInput schema / properties / resume_text / description

Previous value: -"Plain-text resume content extracted by the model from an attached PDF/DOCX/etc. Stored as a text/plain attachment on the candidate. Do not pass binary or base64 here — only the parsed text content."New value: +"Plain text extracted from the resume; stored as a text/plain attachment. No binary or base64."

changedInput schema / properties / stage_id / description

Previous value: -"Pipeline stage ID for the initial application. Requires job_id."New value: +"Initial stage; requires job_id"

removedInput schema / properties / state / description
```
Removed value: -"Candidate state or region."
```

changedInput schema / properties / timezone / description

Previous value: -"IANA timezone (e.g. 'America/Los_Angeles'). Auto-resolved from city/country if omitted."New value: +"IANA, e.g. America/Los_Angeles; resolved from city and country if omitted"

Changed4 schema fields changedJun 7, 2026

addedInput schema / properties / city

Added value: +{
+  "description": "Candidate city for location/timezone resolution.",
+  "type": "string"
+}

addedInput schema / properties / country

Added value: +{
+  "description": "Candidate country name or ISO code.",
+  "type": "string"
+}

addedInput schema / properties / state

Added value: +{
+  "description": "Candidate state or region.",
+  "type": "string"
+}

addedInput schema / properties / timezone

Added value: +{
+  "description": "IANA timezone (e.g. 'America/Los_Angeles'). Auto-resolved from city/country if omitted.",
+  "type": "string"
+}

Changed2 schema fields changedMay 22, 2026

removedInput schema / properties / cv

Removed value: -{
-  "additionalProperties": false,
-  "description": "CV/resume file to attach (base64 payload).",
-  "properties": {
-    "data": {
-      "description": "Base64-encoded file content.",
-      "type": "string"
-    },
-    "file_name": {
-      "description": "Original file name.",
-      "type": "string"
-    },
-    "mime_type": {
-      "description": "MIME type (e.g. application/pdf).",
-      "type": "string"
-    },
-    "size": {
-      "description": "Optional file size in bytes.",
-      "type": "number"
-    }
-  },
-  "required": [
-    "data",
-    "file_name",
-    "mime_type"
-  ],
-  "type": "object"
-}

addedInput schema / properties / resume_text

Added value: +{
+  "description": "Plain-text resume content extracted by the model from an attached PDF/DOCX/etc. Stored as a text/plain attachment on the candidate. Do not pass binary or base64 here — only the parsed text content.",
+  "type": "string"
+}

First observedMay 9, 2026

TDQS

B3.3/5.0

Behavior3/5

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

With readOnlyHint=false and destructiveHint=false, the description carries the burden of behavioral disclosure. It does say the tool creates a candidate and may also create an application, and it sets an expectation that binary data must not be sent, but it does not describe what happens on duplicate email, required identity fields, or likely side effects beyond those already inferable from 'create'.

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?

Two dense sentences, front-loaded with the core purpose and followed by the key resume-handling constraint. There is no filler or redundant overhead.

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

Completeness3/5

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

Given a 13-parameter create operation with no output schema, the description is acceptable but not complete. It does not clarify whether candidate identity fields are mandatory, how duplicate candidates are handled, what IDs are returned, or how an application with job_id/stage_id behaves alongside the candidate creation.

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?

The description adds meaning to job_id/stage_id by calling them an optional application group and explains that resume_text must be extracted plain text, never binary. However, with 13 parameters and 62% schema coverage, it leaves several important parameters such as company_id, last_name, phone, and state to the schema alone without additional context.

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

Purpose4/5

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

The description states the action and resource clearly: create a candidate, optionally with an application and resume text. It is specific enough to separate from most sibling tools, but it does not explicitly differentiate itself from hires_create_application, since both can be tied to a job/application.

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?

The description gives an operative instruction about passing resume_text plain text, but it provides no guidance on when to use this tool versus hires_create_application, hires_update_candidate, or other candidate-related flows. No exclusions, prerequisites, or alternatives are named.

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

All 100Hires - AI ATS & Recruitment Software tools Inspect

Try in Browser

Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

hires_create_candidate

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources