Huntflow MCP Server

list_coworkers

Read-only

Retrieve employees and recruiters for a HuntFlow account using its account ID, with pagination and an optional raw response for full data.

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_coworkers"
  }
}

Input Schema

Name	Required	Description
`raw`	No	Вернуть полный сырой ответ без курирования
`page`	No	Номер страницы (с 1)
`count`	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.5/5.0

Behavior2/5

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

The annotations already declare readOnlyHint=true, so safety is covered; the description adds nothing beyond that — no note on pagination behavior, result size, or whether inactive users are included. It also does not mention that a raw/uncured response can be requested via the raw parameter, which is a meaningful behavioral distinction.

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 certainly short and has zero filler, but it is an under-specified fragment rather than a concise sentence: no verb, no object of the action, no front-loaded statement of what the caller gets back.

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?

With four parameters, an output schema and a read-only annotation, the definition is structurally light — return values need not be described, but the description should still convey that this lists the account's staff/recruiters with pagination. As written it leaves an agent to guess the scope and typical usage.

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%, so account_id, page, count and raw are all documented in the schema itself. The description adds no meaning beyond the schema, so the baseline 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?

"Сотрудники/рекрутеры аккаунта" identifies the resource (employees/recruiters belonging to an account) and usefully disambiguates what a "coworker" is, but it is a bare noun phrase with no verb and largely restates the tool name list_coworkers. It does not distinguish this from sibling list tools beyond the resource noun.

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 another tool (e.g. list_accounts) would be more appropriate. The agent must infer from the name alone that this is the roster lookup for a given account.

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