whed-tools

Overview Schema Source Related Servers Discussions Admin

batch_scrape

Scrape multiple URLs in a single request, with options to render JavaScript and save results as JSON. Useful for collecting data from many pages.

Instructions

Scrape multiple URLs efficiently.

Args:
    urls: List of URLs to scrape
    javascript: Set to True if the sites need JavaScript rendering
    save_path: Optional file path to save all results as a JSON array (e.g. "C:/Users/me/Desktop/batch.json").
               If a directory is given, a timestamped filename is generated automatically.

Returns:
    List of scraping results for each URL

Input Schema

TableJSON Schema

Name	Required	Description	Default
`urls`	Yes
`save_path`	No
`javascript`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Sep 13, 2026

TDQS

A3.5/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 carry the full behavioral burden. It discloses the return shape and the save_path file-writing side effect, but says nothing about rate limits, concurrency, per-URL error handling, permissions, or whether partial failures return partial results.

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 front-loaded with a one-line purpose and then structured into Args and Returns sections. Every element is short and useful, with only the word "efficiently" adding minor fluff.

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 no annotations and a batch operation, the definition is only partly complete. It covers all parameters and the output schema exists, but it lacks behavioral context on failure modes and usage guidance for choosing this tool over siblings.

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 0%, so the description must compensate, and it does: it explains javascript as a JS-rendering switch and save_path as optional with a concrete file-path example and timestamped-directory behavior. It omits URL format constraints and the javascript default, keeping it just short of perfect.

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?

"Scrape multiple URLs efficiently" states a specific verb (scrape) and resource (URLs), and the word "multiple" distinguishes the batch scope from the single-URL sibling scrape_url. An agent can identify what the 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 Guidelines2/5

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

The description offers no when-to-use guidance, no exclusions, and never names an alternative such as scrape_url for single URLs or crawl_website for site traversal. The only implicit cue is the name itself, which is not enough to route between siblings.

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

Deploy Server