Skip to main content
Glama

100Hires - AI ATS & Recruitment Software

by com.100hires
OverviewDiscussionsAdmin

hires_update_candidate

Destructive

Update candidate fields, profile answers or resume text. For an attached resume pass the parsed text via resume_text; never inline binary data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesCandidate id or alias
cityNoAlso used to resolve timezone
emailNo
phoneNo
stateNo
job_idNoCreates a new application for this job
countryNoName or ISO code
profileNoProfile answers keyed by question text or question_id
stage_idNoStage for that application; requires job_id
timezoneNoIANA, e.g. America/Los_Angeles; resolved from city and country if omitted
last_nameNo
first_nameNo
resume_textNoPlain text extracted from the resume; stored as a text/plain attachment. No binary or base64.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed16 schema fields changed
    • 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"
    • changedInput schema / properties / country / description
      Previous value: -"Candidate country name or ISO code."New value: +"Name or ISO code"
    • removedInput schema / properties / email / description
      Removed value: -"Candidate email address."
    • removedInput schema / properties / first_name / description
      Removed value: -"Candidate first name."
    • changedInput schema / properties / id / description
      Previous value: -"Candidate ID (integer) or alias (string)."New value: +"Candidate id or alias"
    • changedInput schema / properties / job_id / description
      Previous value: -"Job ID to create a new application for this candidate."New value: +"Creates a new 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."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 file. Stored as a text/plain attachment. Do not pass binary or base64 — only parsed text."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 application. Requires job_id."New value: +"Stage for that application; 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"
  2. Changed4 schema fields changed
    • 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"
+}
  3. Changed2 schema fields changed
    • 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 file. Stored as a text/plain attachment. Do not pass binary or base64 — only parsed text.",
+  "type": "string"
+}
  4. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already indicate destructiveHint=true, so the description does not need to repeat that. It adds the constraint about resume_text (never inline binary data), which is useful context but not behavioral disclosure. The description does not explain what happens to existing fields when updated (e.g., overwrite behavior) or whether changes are reversible. It adds some value but not enough to exceed a 3.

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 two sentences with no fluff. The primary purpose is front-loaded, and the resume_text note is placed after the general purpose. Every word earns its place. This is exemplary conciseness.

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

Completeness2/5

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

With 13 parameters, a nested profile object, and no output schema, this description is severely under-specified. It does not explain the structure of profile answers, the requirement of job_id for stage_id, the side effect of creating an application, or the expected response. The schema covers some details, but the description adds almost nothing beyond the resume_text constraint. An agent calling this tool would lack critical context for correct invocation.

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 schema covers 62% of parameters with descriptions. The description groups fields into categories (candidate fields, profile answers, resume text) and adds the note that resume_text should be parsed text, which is slightly beyond the schema. However, it does not explain the relationships between job_id and stage_id, the creation of applications, or timezone resolution—details already in the schema. The added value is modest.

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 clearly states the action: 'Update candidate fields, profile answers or resume text.' It specifies the resource (candidate) and the three types of updates, which distinguishes it from sibling tools like hires_update_application or hires_update_company. The verb 'update' is explicit and unambiguous.

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?

The description implies usage (when you need to update a candidate) but provides no explicit guidance on when to choose this over alternatives. It does not mention that other update tools exist for different resources, nor does it note any prerequisites or conditions. The note about resume_text is a constraint, not a usage guideline.

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 toolsInspect
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.

Resources