Skip to main content
Glama

batch_fetch_webpages

Parallel batch webpage and document retrieval tool. Fetches up to 5 public URLs concurrently with fair settlement (returns 502 without settling if all fail), VPS browser concurrency protection, and native Markdown/plain text output.

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_fetch_webpages"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsYesList of 1 to 5 public HTTP/HTTPS URLs to retrieve in parallel.
no_cacheNoBypass cache lookup.
render_modeNoRendering strategy: 'auto' (fast HTTP with browser fallback capped at 2) or 'http_only'.auto
max_chars_per_urlNoMaximum characters returned per URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does real work: it discloses the concurrency ceiling, a browser concurrency guard, the output format (native Markdown/plain text), and a specific failure contract ('returns 502 without settling if all fail'). Gaps remain on partial-failure semantics (what happens when 2 of 5 succeed) and per-URL error reporting.

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?

One front-loaded sentence that packs scope, concurrency behavior, failure mode and output format with no filler. Slightly dense — terms like 'fair settlement' and 'VPS browser concurrency protection' are internal jargon an agent may not fully parse.

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?

No output schema exists, yet the description still states the return format (Markdown/plain text) and the per-URL character cap, which covers most of what an agent needs. It falls short only on the shape of the multi-URL response and partial-failure results.

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, no_cache, render_mode and max_chars_per_url including the 1000-20000 bounds. The description only echoes the 5-URL cap and hints at a browser concurrency cap of 2 for render_mode; it adds no format or behavior detail the schema lacks.

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?

Names a specific verb and resource ('Parallel batch webpage and document retrieval tool') plus a hard scope limit ('up to 5 public URLs concurrently'), which is exactly what separates it from the single-URL siblings like fetch_webpage and render_webpage. An agent can pick it for multi-URL work without opening either schema.

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 'parallel batch' framing implies when to reach for this over a single-page fetch, and the 5-URL ceiling and public-only constraint are stated. But there is no explicit when-to-use/when-not guidance and no sibling named as the alternative for single-URL or authenticated/private fetches.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.