HuntFlow MCP Server

get_applicant_resumes

Retrieve candidate resumes from attached external files to review their application documents and assess qualifications.

Instructions

Резюме кандидата (все прикреплённые external).

Input Schema

TableJSON Schema

Name	Required	Description
`raw`	No	Вернуть полный сырой ответ без курирования
`account_id`	Yes	ID аккаунта HuntFlow
`applicant_id`	Yes	ID кандидата

Output Schema

TableJSON Schema

Name	Required	Description	Default
`page`	No
`count`	No
`items`	No
`total`	No
`total_items`	No
`next_page_cursor`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.1.1Sep 7, 2026

addedInput schema / properties / raw

Added value: +{
+  "description": "Вернуть полный сырой ответ без курирования",
+  "type": "boolean"
+}

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": {
+          "account_source": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "auth_type": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "created": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "id": {
+            "type": "number"
+          },
+          "updated": {
+            "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"
+}

First observedv1.1.0May 29, 2026

TDQS

C2.9/5.0

Behavior2/5

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

The description does not disclose any behavioral aspects beyond the basic function. It does not mention that this is a read-only operation, nor any details about filtering, sorting, pagination, or response format. Since there are no annotations, the description carries the full burden and falls short.

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 extremely concise, consisting of a single short phrase. It contains no redundant words or unnecessary details, making it efficient and to the point.

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?

The description lacks critical context such as clarifying what 'external' means, whether the response includes multiple items, or any indication of the response structure. It is too sparse for an agent to understand the full scope of the tool without additional inference.

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?

Parameter descriptions are provided for all three parameters (account_id, applicant_id, raw), covering 100% of the schema. The tool description itself adds no extra context about how these parameters are used, 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 states the tool retrieves a candidate's resume, specifically all attached external ones. Although brief, it clearly identifies the resource and distinguishes it from other tools like get_resume which likely retrieves a single resume. The verb is implied by the tool name and the description.

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?

The description provides no guidance on when to use this tool versus alternatives such as get_resume or get_applicant. It does not mention any conditions, prerequisites, or typical scenarios, leaving the agent to infer usage from the name and parameter structure.

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

Deploy Server