Skip to main content
Glama
theYahia

HuntFlow MCP Server

by theYahia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

search_applicants

Find candidates in HuntFlow using name, email, or phone, and narrow results by vacancy, recruitment stage, or tag.

Instructions

Поиск кандидатов по имени/email/телефону и фильтрам (вакансия, этап, тег).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoПоиск по имени, email или телефону
rawNoВернуть полный сырой ответ без курирования
tagNoФильтр по ID тега
pageNoНомер страницы (с 1)
countNoКол-во на странице (макс 100)
statusNoФильтр по ID этапа подбора
vacancyNoФильтр по ID вакансии
account_idYesID аккаунта HuntFlow

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
countNo
itemsNo
totalNo
total_itemsNo
next_page_cursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv1.1.1
    • changedInput schema / properties / count / description
      Previous value: -"Количество"New value: +"Кол-во на странице (макс 100)"
    • addedInput schema / properties / page
      Added value: +{
+  "default": 1,
+  "description": "Номер страницы (с 1)",
+  "minimum": 1,
+  "type": "integer"
+}
    • changedInput schema / properties / q / description
      Previous value: -"Поиск по имени или email"New value: +"Поиск по имени, email или телефону"
    • addedInput schema / properties / raw
      Added value: +{
+  "description": "Вернуть полный сырой ответ без курирования",
+  "type": "boolean"
+}
    • addedInput schema / properties / status
      Added value: +{
+  "description": "Фильтр по ID этапа подбора",
+  "type": "number"
+}
    • addedInput schema / properties / tag
      Added value: +{
+  "description": "Фильтр по ID тега",
+  "type": "number"
+}
    • addedInput schema / properties / vacancy
      Added value: +{
+  "description": "Фильтр по ID вакансии",
+  "type": "number"
+}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "count": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "items": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "created": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "email": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "first_name": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "id": {
+            "type": "number"
+          },
+          "last_name": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "middle_name": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "phone": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "position": {
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "next_page_cursor": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "page": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "total": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "total_items": {
+      "type": [
+        "number",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}
  2. First observedv1.1.0

TDQS

B3.2/5.0
Behavior3/5

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

The description clearly indicates a search operation, implying read-only behavior. However, with no annotations, the description carries the full burden for behavioral transparency; it does not explicitly state side effects (e.g., no modification) or mention result format nuances like the 'raw' parameter's effect.

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 a single, concise sentence that immediately conveys the tool's core function and filtering criteria with no redundancy or unnecessary details.

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

Completeness4/5

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

Given the simplicity of the tool and the rich schema documentation, the description is largely complete for an agent to understand the purpose. It could slightly benefit from explicitly stating that results are a list of candidates or that pagination is supported, but these are indirectly inferable from the parameters.

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 coverage is 100% and each parameter has a meaningful description. The tool description itself adds no extra parameter insight beyond what the schema already provides, so the baseline of 3 is appropriate.

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?

States a specific verb (search) and resource (candidates) with clear filtering dimensions (name/email/phone, vacancy, stage, tag). However, it does not explicitly differentiate from sibling tools like list_vacancy_applicants, which may also return candidate lists in a narrower context.

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?

Provides no guidance on when to use this tool versus alternatives such as list_vacancy_applicants or get_applicant. An agent is left to infer the appropriate context from the tool's name and description alone.

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