SurveyHub-MCP

Hunter Enterprise Batch Status

hunter_enterprise_batch_status

Retrieve the progress status of an enterprise batch task from Hunter, using the task ID returned when the task was created.

Instructions

Get Hunter enterprise batch task progress.

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

Input Schema

Name	Required	Description	Default
`task_id`	Yes	Task ID returned by hunter_enterprise_batch_create.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.17.0Jul 15, 2026

TDQS

A3.9/5.0

Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states 'Get ... progress' without explaining that the tool is read-only, whether it can be called multiple times, what happens if the task ID is invalid, or what the response format looks like. This is a significant gap for a tool that checks asynchronous progress.

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 a single, front-loaded sentence that captures the essence of the tool with zero wasted words. It is maximally concise while remaining informative.

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?

Given the low complexity (one parameter, no output schema), the description provides minimal but adequate information. However, it does not specify what 'progress' entails (e.g., status enums, completion percentage) or whether the tool returns immediately or waits. This leaves some ambiguity for an agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema covers 100% of parameters, but the description adds value by specifying that task_id is 'returned by hunter_enterprise_batch_create.' This tells the agent exactly how to obtain a valid task ID, which is more helpful than just the schema type alone.

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 uses a specific verb 'Get' and identifies the resource as 'Hunter enterprise batch task progress.' It clearly distinguishes from sibling tools like hunter_enterprise_batch_create, hunter_enterprise_batch_download, and hunter_enterprise_batch_pull, each of which handles different stages of the batch workflow.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Although the description lacks explicit 'when to use' or 'when not to use' statements, the parameter description for task_id states 'Task ID returned by hunter_enterprise_batch_create,' which implies the tool should be used after creating a batch task to check its progress. This provides indirect usage guidance.

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