Skip to main content
Glama
Sign In
brightdata

Bright Data MCP

Official
by brightdata
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

scrape_batch

Read-only

Fetch up to five web pages in one request and return ordered JSON results with content in markdown, text, HTML, or schema.org data for batch web data extraction.

Instructions

Fetch up to 5 web pages at once. Returns a JSON array in input order, one item per URL: url, title, format, content, or url and error if that page failed. content is the page in one format, markdown by default. Pick another with the format param:

  • text: plain text, no links or headings

  • html: raw HTML, for CSS selectors or data hidden in the markup

  • ld_json: schema.org data (price, rating, author...) If a page has no data in that format, markdown is returned instead, with a note. No JavaScript rendering. Pages that take longer than 35 s time out.

Input Schema

NameRequiredDescriptionDefault
urlsYes
formatNomarkdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv4.2.0
    • addedInput schema / properties / format
      Added value: +{
+  "default": "markdown",
+  "enum": [
+    "markdown",
+    "text",
+    "html",
+    "ld_json"
+  ],
+  "type": "string"
+}
    • removedInput schema / properties / urls / description
      Removed value: -"Array of URLs to scrape (max 5)"
  2. Addedv2.9.3

TDQS

A4.5/5.0
Behavior5/5

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

Adds substantial behavior beyond annotations: returns a JSON array in input order, per-URL success/error shape, default markdown format, fallback to markdown with a note when the requested format has no data, no JavaScript rendering, and a 35 s timeout.

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?

Front-loads the core action and return shape, then uses a compact bullet list for format options. The length is justified by the number of behavioral details and no sentence is wasted.

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

Completeness5/5

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

No output schema exists, but the description fully explains the return structure, error handling, format fallback, timeout, and JavaScript limitation. Combined with annotations covering safety and open-world access, an agent has enough to call it correctly.

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 description coverage is 0%, so the description must carry parameter meaning. It thoroughly explains the format enum values, default, and fallback behavior, and clarifies that urls are processed in input order with a maximum of 5, though it does not restate the URI format constraint.

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 and resource with scope: "Fetch up to 5 web pages at once." The batch nature and return-array behavior distinguish it from single-page siblings like scrape_as_markdown and scrape_as_html.

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?

Explains how to choose a format via the format parameter and notes no JavaScript rendering and a 35 s timeout. However, it does not explicitly say when to use this batch tool versus single-page scrape siblings or search_engine_batch.

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