Skip to main content
Glama
theYahia

HuntFlow MCP Server

by theYahia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

list_vacancies

Retrieve vacancies from HuntFlow ATS with filters for state, ownership, and pagination. Get open, closed, or held positions to manage recruitment pipelines.

Instructions

Список вакансий в HuntFlow (по умолчанию открытые).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rawNoВернуть полный сырой ответ без курирования
mineNoТолько вакансии, где я участник
pageNoНомер страницы (с 1)
countNoКол-во на странице (макс 100)
stateNoФильтр по состоянию (альтернатива opened)
openedNoТолько открытые вакансии
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. Changed6 schema fields changedv1.1.1
    • changedInput schema / properties / count / description
      Previous value: -"Количество"New value: +"Кол-во на странице (макс 100)"
    • addedInput schema / properties / mine
      Added value: +{
+  "description": "Только вакансии, где я участник",
+  "type": "boolean"
+}
    • addedInput schema / properties / page
      Added value: +{
+  "default": 1,
+  "description": "Номер страницы (с 1)",
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / raw
      Added value: +{
+  "description": "Вернуть полный сырой ответ без курирования",
+  "type": "boolean"
+}
    • addedInput schema / properties / state
      Added value: +{
+  "description": "Фильтр по состоянию (альтернатива opened)",
+  "enum": [
+    "OPEN",
+    "CLOSED",
+    "HOLD"
+  ],
+  "type": "string"
+}
    • 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": {
+          "company": {
+            "anyOf": [
+              {
+                "type": [
+                  "string",
+                  "number"
+                ]
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "created": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "id": {
+            "type": "number"
+          },
+          "money": {
+            "$ref": "#/properties/items/items/properties/company"
+          },
+          "position": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "priority": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "state": {
+            "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

C2.5/5.0
Behavior1/5

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

No annotations are provided, so the description must disclose behavioral traits. It mentions no side effects, permissions, rate limits, or pagination behavior, leaving the agent without insight into what happens when the tool is invoked.

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

Conciseness4/5

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

The description is a single, concise sentence without redundant information. It is appropriately sized for a simple list operation, though it lacks additional structure to highlight key aspects.

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 has multiple parameters (including filters like state, opened, mine) and an output schema, the description is too sparse. It does not mention response format, pagination, or how the parameters relate to the returned data, leaving significant gaps for the agent.

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?

The schema already provides full descriptions for all 7 parameters (100% coverage). The tool description adds no additional meaning or clarification beyond the schema, so the baseline score 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?

The description clearly states the tool lists vacancies in HuntFlow, with a note about default open state. It is distinct enough from siblings like get_vacancy and list_accounts, though it does not explicitly contrast them.

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 guidance on when to use this tool versus alternatives such as search_applicants or get_vacancy. The description only provides a basic list function without any usage context or conditions.

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