Crawl-MCP

Overview Schema Source Related Servers Discussions Admin

batch_search_web

Read-only

Run up to three web searches in one call, optionally saving the full JSON results to disk and returning a compact response to reduce token usage.

Instructions

Perform multiple web searches. Max 3 queries per call. Supply output_path in the request to persist the full result set to disk as JSON and receive a slim response.

Input Schema

Name	Required	Description	Default
`request`	Yes	Dict with: queries (max 3), num_results_per_query, search_genre (optional, one of: pdf, documents, presentations, spreadsheets, japanese, english; adds a filetype/language operator to the query, other values return an error), engine (optional, one of: auto, google_custom, brave, exa, searxng; default from SEARCH_ENGINE, auto tries the configured engines in SEARCH_ENGINE_ORDER and moves to the next one on errors other than zero results), result_type (optional; default web; one of web, discussions, faq, videos, news, or several as a list or a comma-separated string; everything except web runs on brave only; news is a separate Brave News Search request; results holds web when requested, else the first type, and the other types go to extra_results; discussions are forum posts with the forum name, answer count, post score, question and top comment; faq are question and answer excerpts; Brave returns these sections for some queries only, and num_results only shortens them), recent_days. Optional persistence keys: output_path (absolute file path, auto .json extension — full result set written to disk), include_content_in_response (bool, default False — when True keeps results in the response too), overwrite (bool, default False).

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.4.2Oct 31, 2026

TDQS

A3.9/5.0

Behavior4/5

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

readOnlyHint=true is consistent with a search operation, so no contradiction. The description contributes real behavior beyond the annotations: the 3-query cap and the fact that supplying output_path makes the response 'slim' while the full set lands on disk - a consequence the annotation does not convey.

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?

Three short sentences, zero waste, and the primary action is front-loaded ahead of the operational constraints. Nothing is buried or repeated from the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given a rich nested schema at 100% coverage and an output schema, the description needs only the operational gotchas - and it supplies the two most important (query cap, persistence behavior). It could still note that result_type alternatives run on Brave only, but that detail lives in the schema.

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?

Schema coverage is 100% and the nested request object documents every key, so baseline would be 3. The description earns extra credit for explaining the observable effect of output_path (slim response), which the schema states only as 'full result set written to disk'.

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

Purpose4/5

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

States a specific verb and resource ('Perform multiple web searches') plus a hard scope limit ('Max 3 queries per call'). It does not explicitly name siblings like search_web or batch_search_google, so the batch-vs-single distinction is left to the name rather than the description.

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 only concrete guidance is a usage rule for persistence ('Supply output_path ... to persist the full result set'), which covers one scenario well. It never says when to choose this over search_web or batch_search_google, so the selection decision must be inferred from the name.

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