Huntflow MCP Server

set_vacancy_state

Close, pause, or resume a Huntflow vacancy by setting its state with optional reason, date, comment, and unpublish flag.

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>",
      "vacancy_id": "<vacancy_id>",
      "action": "<action>"
    },
    "name": "set_vacancy_state"
  }
}

Input Schema

Name	Required	Description
`date`	No	Дата действия (для close/hold), YYYY-MM-DD
`action`	Yes	close — закрыть, hold — приостановить, resume — возобновить
`comment`	No	Комментарий (для close/hold)
`reason_id`	No	ID причины закрытия/приостановки
`account_id`	Yes	ID аккаунта HuntFlow
`vacancy_id`	Yes	ID вакансии
`unpublish_all`	No	Снять вакансию со всех публикаций

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.3.0Nov 11, 2026

TDQS

C2.8/5.0

Behavior2/5

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

Annotations already give readOnly=false, destructive=false, idempotent=false, so the description is free to add what those don't cover — and it adds nothing. It does not say that closing may unpublish the vacancy (implied by the unpublish_all param), whether a reason or comment becomes mandatory for close/hold, or whether the transition is reversible.

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

Conciseness3/5

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

The single sentence is front-loaded and contains no filler, which is good. However it is short by under-specification rather than by economy — it spends its one clause restating the three action names that the action enum already documents.

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 7-parameter, non-idempotent mutation with conditional parameters and no output schema, yet the description says nothing about preconditions, side effects on publications, or outcomes. For a state-changing HR tool where a wrong call closes a live vacancy, that is a substantial gap.

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% and every parameter carries its own Russian description including the action enum values, so the schema fully carries parameter meaning. The one-line description adds no format, dependency, or precedence information (e.g. date/reason_id required only for close/hold) beyond what is already structured.

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 names a specific verb set (close, suspend, resume) against a specific resource (vacancy), so the agent knows exactly what operation family this is. It does not distinguish itself from the sibling update_vacancy, which could plausibly overlap on state fields, so it stops short of a 5.

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?

There is no statement of when to use this tool versus update_vacancy or why a state change must go through this dedicated endpoint. The agent must infer entirely from the tool name that lifecycle transitions belong here and generic edits belong elsewhere.

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