Skip to main content
Glama

100Hires - AI ATS & Recruitment Software

hires_update_job

Destructive

Update a job. Send only the fields to change.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesJob id or alias
titleNo
statusNoFrom hires_list_statuses, e.g. Draft, Public
form_idNoApplication form to assign
includeNoEmbed: workflow, hiring_team, pipeline_stages
languageNoJob page locale, e.g. de-DE; null = follow the career site language, omit = keep current. Values: hires_list_languages
is_remoteNoRemote job; with empty city, state and postal code Indeed posts it nationwide
salary_maxNo
salary_minNo
category_idNoFrom hires_list_categories
descriptionNoHTML allowed
workflow_idNoWorkflow to assign
department_idNoFrom hires_list_departments
location_cityNoEmpty string clears it; remote without city = nationwide posting on Indeed
parent_job_idNoParent job; makes this a satellite job
salary_periodNo
internal_titleNoHiring team only
location_stateNo
internal_job_idNoExternal reference id
salary_currencyNoISO code, e.g. USD
location_countryNo
education_level_idNoFrom hires_list_education_levels
employment_type_idNoFrom hires_list_employment_types
knockout_questionsNoYes/No screening questions added to the application form
ai_scoring_criteriaNoDiff-replace by id: with id update, without id create, absent ones are removed; [] detaches all; omit to keep
experience_level_idNoFrom hires_list_experience_levels
resume_field_statusNo
location_postal_codeNo
location_full_addressNo
location_street_addressNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed41 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / ai_scoring_criteria / description
      Previous value: -"AI scoring criteria for evaluating candidates. Diff-replace by id: items with id update existing, items without id create new, existing criteria not in payload are removed. Omit to leave existing criteria untouched. Pass [] to detach all."New value: +"Diff-replace by id: with id update, without id create, absent ones are removed; [] detaches all; omit to keep"
    • removedInput schema / properties / ai_scoring_criteria / items / additionalProperties
      Removed value: -false
    • changedInput schema / properties / ai_scoring_criteria / items / properties / id / description
      Previous value: -"ID of an existing criterion attached to this job. With id → update in place; without id → create new. Items on the job not referenced by id are removed."New value: +"Existing criterion id; omit to create"
    • changedInput schema / properties / ai_scoring_criteria / items / properties / text / description
      Previous value: -"Prompt text describing what to evaluate."New value: +"What to evaluate"
    • removedInput schema / properties / ai_scoring_criteria / items / properties / title / description
      Removed value: -"Optional short label for the criterion."
    • changedInput schema / properties / ai_scoring_criteria / items / properties / weight / description
      Previous value: -"Relative importance (1–10)."New value: +"Relative importance"
    • changedInput schema / properties / category_id / description
      Previous value: -"Job category ID from GET /taxonomy/categories."New value: +"From hires_list_categories"
    • changedInput schema / properties / department_id / description
      Previous value: -"Department ID from GET /taxonomy/departments."New value: +"From hires_list_departments"
    • changedInput schema / properties / description / description
      Previous value: -"Job description (HTML allowed)."New value: +"HTML allowed"
    • changedInput schema / properties / education_level_id / description
      Previous value: -"Education level ID from GET /taxonomy/education-levels."New value: +"From hires_list_education_levels"
    • changedInput schema / properties / employment_type_id / description
      Previous value: -"Employment type ID from GET /taxonomy/employment-types."New value: +"From hires_list_employment_types"
    • changedInput schema / properties / experience_level_id / description
      Previous value: -"Experience level ID from GET /taxonomy/experience-levels."New value: +"From hires_list_experience_levels"
    • changedInput schema / properties / form_id / description
      Previous value: -"Application form ID to assign to this job."New value: +"Application form to assign"
    • changedInput schema / properties / id / description
      Previous value: -"Job ID (numeric) or alias"New value: +"Job id or alias"
    • changedInput schema / properties / include / description
      Previous value: -"Comma-separated related resources to embed: workflow, hiring_team, pipeline_stages"New value: +"Embed: workflow, hiring_team, pipeline_stages"
    • changedInput schema / properties / internal_job_id / description
      Previous value: -"External reference ID from your ATS or HR system."New value: +"External reference id"
    • changedInput schema / properties / internal_title / description
      Previous value: -"Internal-only title visible to the hiring team."New value: +"Hiring team only"
    • changedInput schema / properties / is_remote / description
      Previous value: -"Whether this is a remote position."New value: +"Remote job; with empty city, state and postal code Indeed posts it nationwide"
    • changedInput schema / properties / knockout_questions / description
      Previous value: -"Boolean knockout questions added to the application form."New value: +"Yes/No screening questions added to the application form"
    • removedInput schema / properties / knockout_questions / items / additionalProperties
      Removed value: -false
    • changedInput schema / properties / knockout_questions / items / properties / disqualify_on_wrong_answer / description
      Previous value: -"If true, applicants who answer incorrectly are automatically disqualified."New value: +"Disqualify on wrong answer"
    • removedInput schema / properties / knockout_questions / items / properties / expected_answer / description
      Removed value: -"The correct/desired answer."
    • changedInput schema / properties / knockout_questions / items / properties / text / description
      Previous value: -"Question text shown to the applicant."New value: +"Shown to the applicant"
    • addedInput schema / properties / language
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maxLength": 35,
      +      "minLength": 1,
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Job page locale, e.g. de-DE; null = follow the career site language, omit = keep current. Values: hires_list_languages"
      +}
    • changedInput schema / properties / location_city / description
      Previous value: -"Job city."New value: +"Empty string clears it; remote without city = nationwide posting on Indeed"
    • removedInput schema / properties / location_country / description
      Removed value: -"Job country."
    • removedInput schema / properties / location_full_address / description
      Removed value: -"Full formatted address."
    • removedInput schema / properties / location_postal_code / description
      Removed value: -"Postal or ZIP code."
    • removedInput schema / properties / location_state / description
      Removed value: -"Job state or region."
    • removedInput schema / properties / location_street_address / description
      Removed value: -"Street address."
    • changedInput schema / properties / parent_job_id / description
      Previous value: -"Canonical parent job ID. If provided, the job becomes a satellite job."New value: +"Parent job; makes this a satellite job"
    • removedInput schema / properties / resume_field_status / description
      Removed value: -"Resume field behavior on the application form."
    • changedInput schema / properties / salary_currency / description
      Previous value: -"Salary currency code (e.g. USD, EUR)."New value: +"ISO code, e.g. USD"
    • removedInput schema / properties / salary_max / description
      Removed value: -"Maximum salary."
    • removedInput schema / properties / salary_min / description
      Removed value: -"Minimum salary."
    • removedInput schema / properties / salary_period / description
      Removed value: -"Salary period."
    • changedInput schema / properties / status / description
      Previous value: -"Job status (e.g. Draft, Public). See GET /taxonomy/statuses."New value: +"From hires_list_statuses, e.g. Draft, Public"
    • removedInput schema / properties / title / description
      Removed value: -"Public job title."
    • changedInput schema / properties / workflow_id / description
      Previous value: -"Workflow ID to assign to this job."New value: +"Workflow to assign"
  2. Changed1 schema field changed
    • addedInput schema / properties / ai_scoring_criteria
      Added value: +{
      +  "description": "AI scoring criteria for evaluating candidates. Diff-replace by id: items with id update existing, items without id create new, existing criteria not in payload are removed. Omit to leave existing criteria untouched. Pass [] to detach all.",
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "id": {
      +        "description": "ID of an existing criterion attached to this job. With id → update in place; without id → create new. Items on the job not referenced by id are removed.",
      +        "exclusiveMinimum": 0,
      +        "type": "integer"
      +      },
      +      "text": {
      +        "description": "Prompt text describing what to evaluate.",
      +        "type": "string"
      +      },
      +      "title": {
      +        "description": "Optional short label for the criterion.",
      +        "type": "string"
      +      },
      +      "weight": {
      +        "description": "Relative importance (1–10).",
      +        "maximum": 10,
      +        "minimum": 1,
      +        "type": "integer"
      +      }
      +    },
      +    "required": [
      +      "text",
      +      "weight"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
  3. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already indicate destructiveHint=true and readOnlyHint=false, so the description's role is limited. It adds the partial-update behavior ('Send only the fields to change'), implying omitted fields are preserved. This is useful context but does not cover side effects like job board re-posting or array diff-replacement, which are detailed only 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.

Conciseness4/5

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

The description is extremely concise—two short sentences with no filler. It front-loads the purpose and includes a critical usage instruction. However, given the tool's 30 parameters and complexity, a slightly more structured description could have provided additional guidance without becoming verbose.

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?

Despite the tool's complexity (30 parameters, no output schema, destructive annotations), the description is minimal. It fails to mention key behavioral details like the diff-replace semantics for arrays, remote job implications, or the fact that fields not sent are left unchanged (beyond the implicit 'send only fields to change'). The schema covers many details, but the description does not synthesize them for the agent, leaving significant context gaps.

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 67%, and the schema provides detailed descriptions for many parameters, including references to list tools and enums. The tool description itself does not add any parameter-level information beyond what the schema already offers. With moderate coverage, the description does not compensate for gaps, so it adds minimal value.

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 clearly states 'Update a job', which is a specific verb and resource. It distinguishes from create/delete tools, but not from hires_set_job_status, which is a more specialized sibling that also updates job fields. However, the name and description make the primary purpose 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 instruction 'Send only the fields to change' provides a clear usage rule for partial updates, but it does not offer guidance on when to use this tool versus alternatives like hires_set_job_status. No exclusions or alternative routing are given, leaving the agent to infer the distinction.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.