SurveyHub-MCP

Hunter Enterprise Batch Pull

hunter_enterprise_batch_pull

Pull enterprise batch task results from Hunter as JSON. Use task ID to get paginated data.

Instructions

Pull Hunter enterprise batch task results as JSON. Enterprise-only.

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

Input Schema

Name	Required	Description
`page`	No	Page number.
`task_id`	Yes	Task ID returned by hunter_enterprise_batch_create.
`page_size`	No	Results per page.

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, so the description carries full burden. It does not disclose behavior such as whether results are only available after task completion, rate limits, or error states. The pagination parameters are documented in schema but not described behaviorally.

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?

Extremely concise: one sentence plus scope qualifier. No wasted words. Could be slightly more informative without losing conciseness, but still well-structured for its length.

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?

No output schema, so description should at least hint at return format ('as JSON' helps slightly). However, missing details like whether it returns a list or object, pagination behavior, and handling of incomplete tasks make it incomplete for effective use.

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% with clear parameter descriptions (e.g., task_id links to batch_create). The tool description adds no extra semantic value beyond the schema, earning the baseline score of 3.

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 ('Pull') and resource ('batch task results'), and clearly distinguishes from sibling tools like batch_create and batch_status by focusing on results retrieval. 'Enterprise-only' further clarifies scope.

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 like hunter_enterprise_batch_download or hunter_enterprise_batch_status. The description only mentions 'Enterprise-only' but doesn't explain prerequisites or ordering relative to other batch operations.

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