Huntflow MCP Server

list_sources

Read-only

Retrieves the candidate source directory for a Huntflow account so you can identify where applicants originate and support recruiting analytics.

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

Input Schema

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

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.6/5.0

Behavior2/5

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

The only annotation, readOnlyHint=true, already tells the agent this is a safe read. The description adds nothing beyond that: it does not say whether results are account-scoped, whether the list is paginated or complete, or what the curated versus raw response distinction implies in practice.

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

Conciseness3/5

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

It is a single short sentence fragment with zero waste, but its brevity reads as under-specification rather than disciplined conciseness. Nothing is front-loaded because there is essentially nothing to front-load.

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?

This is a simple two-parameter read tool with full schema coverage, an output schema, and a read-only annotation, so the structured fields carry most of the burden. Still, the description leaves the agent with no statement of purpose timing or sibling routing, which is a real gap even for a tool this simple.

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%, with both account_id and raw documented in the schema itself, so the description is not required to compensate. It contributes no additional parameter meaning, which merits the baseline score rather than more.

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?

"Справочник источников кандидатов" names the resource (a reference list of candidate sources), which adds a bit of domain specificity beyond the bare name list_sources. However, there is no verb and no differentiation from the many sibling list_* tools (list_tags, list_stages, list_divisions), so an agent must infer that this is a retrieval operation.

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 contains no when-to-use or when-not-to-use guidance and never references alternatives. An agent is left to guess that this is the appropriate call when it needs source identifiers for applicants, and no exclusions or prerequisites are stated.

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