Skip to main content
Glama
Sign In
webclaw

webclaw

by 0xMassi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

batch

Extract content from multiple URLs concurrently to process web data efficiently. Specify concurrency levels and output formats for streamlined content collection.

Instructions

Extract content from multiple URLs concurrently.

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": {
      "urls": "<urls>"
    },
    "name": "batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
concurrencyNoNumber of concurrent requests (default: 5)
formatNoOutput format: "markdown" (default), "llm", "text"
urlsYesList of URLs to extract content from

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description must carry full behavioral disclosure. It successfully mentions 'concurrently' indicating parallel execution, but lacks critical safety information for a network tool: error handling behavior (what happens if one URL fails?), timeout behavior, rate limiting, or whether results preserve input ordering.

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?

Extremely efficient at 6 words. Front-loaded with action verb ('Extract') and scope ('multiple URLs concurrently'). Zero redundancy or filler content. Every word earns its place without requiring editing.

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?

With 100% input schema coverage, the description need not elaborate on parameters. However, lacking both annotations and output schema, the description should disclose error behavior or return structure for this concurrent network operation. It is minimal but adequate given the straightforward nature of the operation and good schema coverage.

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 description coverage is 100% (concurrency, format, urls all documented), establishing baseline 3. The description implies the 'urls' parameter through 'multiple URLs' but adds no semantic detail beyond what the schema already provides for parameters (no syntax examples, no clarification of 'llm' format value, no default explanations).

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?

The description uses specific verb 'Extract' and resource 'content from multiple URLs', and includes 'concurrently' which hints at the batch nature. However, it does not explicitly distinguish this from the sibling 'extract' tool (likely single-URL) or 'crawl' (which may also handle multiple URLs), leaving some ambiguity about when to choose this specific tool.

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 provides no guidance on when to use this tool versus alternatives like 'extract', 'scrape', or 'crawl'. It does not mention prerequisites, rate limiting considerations, or appropriate use cases for concurrent processing versus sequential operations.

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

Deploy Server

Other Tools