Hydrafetch

Batch

batch

Scrape a list of URLs you already have, such as pages found with map. Waits for the batch to finish and returns the first page of results in the same call, so a short list needs one call; read further pages, or a batch still running, with batch_status. Each URL scraped costs 1 credit.

Input Schema

TableJSON Schema

Name	Required	Description
`urls`	Yes	The URLs to scrape.
`wait`	No	Seconds to wait for the batch before returning (default 45). 0 returns the batch id at once.
`limit`	No	Results to return in this call (default 10).
`maxCharsPerPage`	No	Cut each page's markdown to this many characters; a cut page says so in data.truncated with its full length. Use it when results are too large for your context.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 21, 2026

addedInput schema / properties / maxCharsPerPage

Added value: +{
+  "description": "Cut each page's markdown to this many characters; a cut page says so in data.truncated with its full length. Use it when results are too large for your context.",
+  "maximum": 9007199254740991,
+  "minimum": 500,
+  "type": "integer"
+}

Changed2 schema fields changedOct 10, 2026

addedInput schema / properties / limit

Added value: +{
+  "description": "Results to return in this call (default 10).",
+  "maximum": 25,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / wait

Added value: +{
+  "description": "Seconds to wait for the batch before returning (default 45). 0 returns the batch id at once.",
+  "maximum": 55,
+  "minimum": 0,
+  "type": "integer"
+}

Changed1 schema field changedSep 7, 2026
- changedInput schema / properties / urls / maxItems
```
Previous value: -1000New value: +25000
```
AddedSep 3, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations declare readOnlyHint=false, openWorldHint=true, destructiveHint=false, so the agent knows this is not a pure read and may reach the open web. The description adds important behavior beyond that: it waits for the batch to finish, returns only the first page in the same call, routes further pages to batch_status, and discloses that each URL costs 1 credit. It does not cover authentication or rate limits, but the cost disclosure is a valuable addition.

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 sentences with no waste: purpose first, then behavior and routing to batch_status, then cost. Front-loaded and appropriately sized.

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?

For a batch-scraping tool with no output schema, the description covers purpose, usage, waiting behavior, pagination, and cost. It could say more about the return format (e.g., markdown pages), but the schema's maxCharsPerPage description partly compensates.

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 the schema already documents urls, wait, limit, and maxCharsPerPage completely. The description adds no parameter syntax or format details beyond that, so the baseline of 3 applies.

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?

States a specific verb (scrape) and resource (list of URLs) and distinguishes itself from map (which finds URLs) and scrape (single URL) by implication. An agent can tell what this tool does without opening the schema.

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?

Names the source of URLs ('pages found with map') and gives an explicit alternative for reading further pages or a running batch ('batch_status'). It does not explicitly exclude single-URL scraping, but the 'list of URLs' framing makes the boundary clear.

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

All Hydrafetch tools Inspect

Try in Browser

Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?