Skip to main content
Glama

hunter_batch_task_create

Create asynchronous batch query tasks on Qianxin Hunter to export asset data to CSV. Upload a file with IPs, domains, or companies, or use search syntax. Returns a task ID for progress tracking and file download.

Instructions

创建 Qianxin Hunter 批量查询任务,任务将以异步方式导出数据为csv。支持通过上传文件(file_path)对批量的ip/domain/company进行资产查询和结果导出,或通过搜索语法(search)进行资产查询和结果导出。成功调用后将返回 task_id,用于后续查询进度和下载文件。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
searchNo搜索语法(与 file_path 二选一提供)。
file_pathNo包含检索目标的本地 CSV 文件路径(与 search 二选一提供)。
start_timeNo开始时间,格式为 YYYY-MM-DD(超出近30天将扣除积分)。
end_timeNo结束时间,格式为 YYYY-MM-DD(超出近30天将扣除积分)。
is_webNo资产类型,1代表”web资产“,2代表”非web资产“,3代表”全部“,默认"全部"。
status_codeNo状态码列表,以逗号分隔,如”200,401“。
fieldsNo可选返回字段,以逗号分隔(如 ip,port,domain 等)。默认为空代表选择权限内所有可导出字段。可选字段枚举: ip,port,domain,ip_tag,url,web_title,is_risk_protocol,protocol,base_protocol,status_code,os,company,number,icp_exception,country,province,city,is_web,isp,as_org,cert_sha256,ssl_certificate,component,asset_tag,updated_at,header,header_server,banner,whois,body,vul_list
search_typeNo上传文件的类型,枚举值:all、ip、domain、company,默认为all。all
assets_limitNo预期导出的资产数量。

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It correctly states the tool is asynchronous, returns a task_id, and exports CSV. However, it does not mention credit costs (hinted in parameters), destructive potential, or authorization requirements.

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?

The description is concise (4 sentences) and front-loaded with the main purpose. It efficiently covers multiple modes and the return value, though there is slight redundancy between the first and third sentences.

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 9 parameters and an output schema, the description is adequate but could be more complete. It mentions async behavior and return of task_id but omits credit costs, prerequisites, and explicit next steps (though hinted).

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 reinforces mutual exclusivity of search and file_path but adds no additional semantic meaning beyond what the parameter descriptions provide.

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 tool creates a batch query task for Qianxin Hunter, specifying asynchronous CSV export and two input modes (file upload or search syntax). This distinguishes it from sibling tools like hunter_search (single search) and the other batch task tools (progress check, download).

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

Usage Guidelines3/5

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

The description implies usage for batch/async queries but does not explicitly guide when to choose this tool over alternatives like hunter_search. It mentions two modes (file_path vs search) but lacks exclusions or comparative guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/PiggyHurry/hunter-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server