SurveyHub-MCP

Hunter Personal Batch Download

hunter_personal_batch_download

Download completed Hunter personal batch export file to a specified local CSV path.

Instructions

Download Hunter personal batch task export file to output_path.

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": {
      "task_id": "<task_id>",
      "output_path": "<output_path>"
    },
    "name": "hunter_personal_batch_download"
  }
}

Input Schema

Name	Required	Description	Default
`task_id`	Yes	Task ID returned by hunter_personal_batch_create.
`output_path`	Yes	Local output CSV path.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.17.0Jul 15, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations provided, and the description fails to disclose behavioral traits such as error handling, file overwrite behavior, or network dependencies. The description is too minimal for a download operation.

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?

One short sentence, no wasted words. However, it could be slightly more informative without losing conciseness.

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 no output schema and simple tool, the description is too minimal. It does not explain prerequisites (e.g., task must be complete), return value, or error scenarios, leaving agents uninformed.

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 coverage is 100%, so baseline is 3. The description adds no new parameter meaning beyond what the schema already provides (task_id and output_path descriptions are identical).

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

Purpose5/5

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

The description clearly states the action ('Download') and resource ('Hunter personal batch task export file'), distinguishing it from siblings like 'hunter_personal_batch_create' and 'hunter_enterprise_batch_download'.

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?

No guidance on when to use this tool versus alternatives (e.g., enterprise version), nor any prerequisites like task completion. The description only states the basic operation.

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