Skip to main content
Glama

100Hires - AI ATS & Recruitment Software

hires_create_job

Create a job. Required: status, title, description, location_country; location_city unless is_remote is true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYes
statusYesFrom hires_list_statuses, e.g. Draft, Public
form_idNoOmitted = new form named after the job
includeNoEmbed: workflow, hiring_team, pipeline_stages
languageNoJob page locale, e.g. de-DE; null = follow the career site language. Values: hires_list_languages
is_remoteNoRemote job; with empty city, state and postal code Indeed posts it nationwide
company_idNo
salary_maxNo
salary_minNo
category_idNoFrom hires_list_categories
descriptionYesHTML allowed
workflow_idNoOmitted = new workflow named after the job
department_idNoFrom hires_list_departments
location_cityNoRequired unless is_remote; empty = nationwide remote 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_countryYes
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_criteriaNoAI scoring criteria for ranking applicants
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. Changed42 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. Pass [] to detach all."New value: +"AI scoring criteria for ranking applicants"
    • 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"
    • 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 / 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. If omitted, a new form named after the job title is created with default questions."New value: +"Omitted = new form named after the job"
    • 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. Values: hires_list_languages"
      +}
    • changedInput schema / properties / location_city / description
      Previous value: -"Job city."New value: +"Required unless is_remote; empty = nationwide remote 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 created 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. If omitted, a new workflow named after the job title is created with default stages."New value: +"Omitted = new workflow named after the job"
    • changedInput schema / required
      Previous value: -[
      -  "status",
      -  "title",
      -  "description",
      -  "location_city",
      -  "location_country"
      -]New value: +[
      +  "status",
      +  "title",
      +  "description",
      +  "location_country"
      +]
  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. 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

C2.8/5.0
Behavior2/5

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

Annotations already indicate a write operation (readOnlyHint=false) and non-destructive behavior (destructiveHint=false). The description adds no behavioral context beyond 'Create a job,' such as side effects (auto-created form/workflow), response behavior, or permission requirements.

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?

A single sentence with zero filler; the core action is front-loaded and the only additional content is a compact list of required or conditional fields. Every word earns its place.

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?

This is a 30-parameter creation tool with no output schema and limited behavioral guidance. The description only covers mandatory input basics, leaving the agent without context on return values, optional-field dependencies, default side effects, or when to supply related object IDs from list_* endpoints.

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

Parameters2/5

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

The description restates required fields that are already in the schema's 'required' array and repeats the location_city/is_remote condition already present in the schema. With 63% schema coverage, it does not meaningfully document the remaining 11 undocumented parameters or add new semantic 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?

'Create a job' clearly states the verb and resource, and the required-field list adds a concrete scope. It is distinguishable from sibling create_* tools, though the phrasing largely restates the tool name.

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 no guidance on when to use this tool versus alternatives such as hires_update_job or hires_create_application. It does not mention exclusions, prerequisites, or scenarios where a sibling would be more appropriate.

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.