Huntflow MCP Server

create_vacancy

Creates a new Huntflow vacancy with title, account, salary, requirements, conditions, deadline, priority, and hiring target for recruiting workflows.

Instructions

Создать вакансию.

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": {
      "account_id": "<account_id>",
      "position": "<position>"
    },
    "name": "create_vacancy"
  }
}

Input Schema

Name	Required	Description
`body`	No	Обязанности (HTML)
`money`	No	Зарплата (строкой)
`hidden`	No	Скрыть вакансию от коллег
`company`	No	Отдел (игнорируется, если включены подразделения)
`deadline`	No	Срок закрытия вакансии, YYYY-MM-DD
`position`	Yes	Название вакансии (должность)
`priority`	No	0 — обычный, 1 — высокий
`account_id`	Yes	ID аккаунта HuntFlow
`conditions`	No	Условия (HTML)
`requirements`	No	Требования (HTML)
`account_region`	No	ID региона
`account_division`	No	ID подразделения (см. list_divisions)
`applicants_to_hire`	No	Сколько человек нужно нанять

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.3.0Nov 11, 2026

TDQS

D1.9/5.0

Behavior2/5

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

Annotations declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the basic mutation profile is known. The description adds nothing beyond that: no required account/permission context, no note that account_id and position are mandatory, no side effects such as hidden visibility or how defaults like applicants_to_hire=1 behave.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

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

One short sentence is structurally clean, but brevity here is under-specification rather than conciseness. There are no wasted words because there are almost no words at all.

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

Completeness1/5

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

For a 13-parameter mutation tool with no output schema, the description is grossly incomplete. It offers no guidance on required fields, HTML formatting expectations, date format, priority semantics, or division/company interaction, all of which an agent must discover from the schema alone.

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 13 parameters already carry meaningful descriptions in the schema, including the division/company interaction and the priority enum values. The description contributes no extra parameter meaning, but the baseline of 3 is appropriate when the schema does the heavy lifting.

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

Purpose2/5

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

The description 'Создать вакансию.' merely restates the tool name in Russian with no additional scope, target resource detail, or distinguishing information. It is a tautology of the name rather than an explanation of what the tool does.

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

Usage Guidelines1/5

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

There is no when-to-use guidance, no mention of alternatives such as update_vacancy or create_applicant, and no prerequisites or exclusions. The agent is left to infer everything from the sibling names.

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