Huntflow MCP Server

get_applicant_resumes

Read-only

Fetch all resumes attached to a Huntflow applicant using account and applicant IDs; optionally return the full raw response instead of curated data.

Instructions

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

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>"
    },
    "name": "get_applicant_resumes"
  }
}

Input Schema

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

Output 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.

First observedv1.3.0Nov 11, 2026

TDQS

C2.4/5.0

Behavior2/5

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

readOnlyHint=true already tells the agent this is a safe read. The description adds only that all attached external resumes are returned, which is a small behavioral detail; nothing is said about what happens when no resume exists, how 'external' attachments differ, or what the raw flag changes at a behavioral level. With annotations covering safety, this is thin but not contradictory.

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

Conciseness2/5

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

It is short, but the brevity comes from under-specification rather than economy: a single parenthetical fragment with no front-loaded verb or object clause. There is no wasted word, but there is also no structure an agent can anchor on.

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 tool is simple, has full schema coverage, an output schema, and a readOnly annotation, so the bar is low. Still, the description leaves the key ambiguity unresolved — how this differs from get_resume and what 'external' means — which is exactly the gap structured fields cannot fill.

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% — account_id, applicant_id, and raw are all documented in the schema itself. The description adds no meaning beyond that, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Резюме кандидата (все прикреплённые external)' names the resource (an applicant's resumes) and narrows scope to all attached external files, which goes slightly beyond the tool name. But it is a bare noun phrase with no verb describing the retrieval action, and it never explicitly contrasts with the sibling get_resume, so the agent must infer the distinction from names alone.

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 when-to-use guidance, no prerequisites, and no mention of when to prefer this over get_resume or get_applicant, despite those being obvious siblings. The parenthetical scope hint is the only signal, and it implies rather than states usage.

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