100Hires MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

hires_create_job

Create a job posting with taxonomy, location, salary, and workflow settings. Provide title, description, city, and country to publish it programmatically.

Instructions

Create a job with taxonomy, location, salary, and workflow configuration. Primary endpoint for programmatic job publishing. Required fields: status, title, description, location_city, location_country.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "status": "<status>",
      "title": "<title>",
      "description": "<description>",
      "location_city": "<location_city>",
      "location_country": "<location_country>"
    },
    "name": "hires_create_job"
  }
}

Input Schema

Name	Required	Description
`title`	Yes	Public job title.
`status`	Yes	Job status (e.g. Draft, Public). See GET /taxonomy/statuses.
`form_id`	No	Application form ID. If omitted, a new form named after the job title is created with default questions.
`include`	No	Comma-separated related resources to embed: workflow, hiring_team, pipeline_stages
`is_remote`	No	Whether this is a remote position.
`company_id`	No	Target company ID. Required only when the API key has access to multiple companies.
`salary_max`	No	Maximum salary.
`salary_min`	No	Minimum salary.
`category_id`	No	Job category ID from GET /taxonomy/categories.
`description`	Yes	Job description (HTML allowed).
`workflow_id`	No	Workflow ID. If omitted, a new workflow named after the job title is created with default stages.
`department_id`	No	Department ID from GET /taxonomy/departments.
`location_city`	Yes	Job city.
`parent_job_id`	No	Canonical parent job ID. If provided, the created job becomes a satellite job.
`salary_period`	No	Salary period.
`internal_title`	No	Internal-only title visible to the hiring team.
`location_state`	No	Job state or region.
`internal_job_id`	No	External reference ID from your ATS or HR system.
`salary_currency`	No	Salary currency code (e.g. USD, EUR).
`location_country`	Yes	Job country.
`education_level_id`	No	Education level ID from GET /taxonomy/education-levels.
`employment_type_id`	No	Employment type ID from GET /taxonomy/employment-types.
`knockout_questions`	No	Boolean knockout questions added to the application form.
`experience_level_id`	No	Experience level ID from GET /taxonomy/experience-levels.
`resume_field_status`	No	Resume field behavior on the application form.
`location_postal_code`	No	Postal or ZIP code.
`location_full_address`	No	Full formatted address.
`location_street_address`	No	Street address.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.3Aug 1, 2026

TDQS

A3.6/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only mentions the action and scope. It fails to disclose important side effects such as automatic creation of a default form or workflow when form_id or workflow_id are omitted, or whether the job is published immediately based on status. This is a significant gap for a create tool with 28 parameters.

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 three concise sentences, front-loaded with the primary action. It avoids redundancy and fluff, with each sentence contributing either purpose, usage context, or essential required-field information. This is appropriately sized for a 28-parameter tool.

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?

Given the tool's complexity (28 parameters, no output schema, no annotations), the description is insufficient. It does not explain return values, side effects like default form/workflow creation, or how status affects publishing. The schema describes parameters but cannot compensate for missing high-level behavioral and output context.

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 all 28 parameters are documented. The description adds only high-level grouping ('taxonomy, location, salary, and workflow configuration') and repeats required fields, which is already in the schema. It does not add meaningful detail beyond the schema, warranting the baseline score of 3.

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 tool's function: 'Create a job' with taxonomy, location, salary, and workflow configuration. It also positions it as the 'Primary endpoint for programmatic job publishing,' distinguishing it from siblings like hires_update_job, hires_delete_job, and hires_set_job_status.

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

Usage Guidelines4/5

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

The description provides clear context for when to use this tool: 'Primary endpoint for programmatic job publishing.' It implies this is the go-to creation tool for jobs, but it does not explicitly mention alternatives or when-not-to-use scenarios, such as 'use hires_update_job to modify an existing job.'

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

Deploy Server