Skip to main content
Glama
Sign In
Huntflow MCP Server

Huntflow MCP Server

by urfan03
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

change_applicant_status

Move a candidate to another hiring stage for a vacancy, including rejection with a reason or hiring, by specifying account, applicant, vacancy, and status IDs.

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>",
      "applicant_id": "<applicant_id>",
      "vacancy_id": "<vacancy_id>",
      "status_id": "<status_id>"
    },
    "name": "change_applicant_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
commentNoКомментарий
status_idYesID этапа подбора (см. list_stages)
account_idYesID аккаунта HuntFlow
vacancy_idYesID вакансии
applicant_idYesID кандидата
fill_quota_idNoID квоты — для этапа «принят»
employment_dateNoДата выхода на работу — для этапа «принят»
rejection_reason_idNoID причины отказа (см. list_rejection_reasons) — для этапа «отказ»

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already say this is a mutation (readOnlyHint=false) and not idempotent, so the description needs to explain only the additional behavior. The description adds useful domain context that the operation can record a rejection or a hire, but it does not say what happens to the candidate's history, the required permissions, or what repeated calls do.

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?

It is a single front-loaded sentence that establishes the action and scope immediately, with the parenthetical variant detail placed where it does the most good and no wasted wording.

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

Completeness3/5

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

For an 8-parameter mutation with no output schema, the description covers the core action and the two special modes, but it leaves out transition validity, failure behavior, and side effects such as history or notification changes.

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 the schema already tags status_id, rejection_reason_id, fill_quota_id, and employment_date with their stage contexts. The description's mention of rejection and hire corroborates that design but adds no new syntax or mapping beyond what the schema states.

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 gives a specific verb+resource: moving a candidate to another recruitment stage for a given vacancy, and it names the notable variants (rejection with a reason, hire). It clearly differs from sibling tools such as add_applicant_to_vacancy or set_vacancy_state, though it does not explicitly name any of them.

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 description hints at when certain modes apply (rejection with reason, hire), but it never states when to use this tool instead of alternatives or what prerequisites are needed. The guidance is implied rather than explicit.

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

Deploy Server

Other Tools