Skip to main content
Glama

Bright Data

by io.github.pipeworx-io

Brightdata Unlock

brightdata_unlock
Read-onlyIdempotent

Fetch any URL through Bright Data Web Unlocker — rotating residential proxies with automatic anti-bot bypass and CAPTCHA solving, built for the hardest-to-scrape sites (Cloudflare, PerimeterX, Akamai fronted). Returns the page content with status and length; large pages are truncated. Calls proxy the fetch synchronously and can take 10-30 seconds. BYOK: Bright Data API token via _apiKey + a Web Unlocker zone configured in your dashboard (first zone is auto-named "web_unlocker1"); pay-per-request pricing on the Bright Data side. Example: brightdata_unlock({ url: "https://example.com", _apiKey: "your-brightdata-token" })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe absolute URL to fetch, including scheme, e.g. "https://example.com/page"
zoneNoYour Web Unlocker zone name from the Bright Data control panel. Default "web_unlocker1" — the auto-generated name of the first Web Unlocker zone.
formatNoResponse shape: "raw" (default — the target page body as a string) or "json" (a JSON envelope with status/headers/body metadata from Bright Data).
_apiKeyYesYour Bright Data API token (account settings or zone Overview tab). Requires a Bright Data account with a Web Unlocker zone; sign up at https://brightdata.com
countryNoTwo-letter ISO country code for the proxy exit location, e.g. "us", "gb", "de". Default: Bright Data auto-selects per your zone configuration.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-brightdata-token",
+    "url": "https://example.com/page"
+  },
+  {
+    "_apiKey": "your-brightdata-token",
+    "country": "us",
+    "format": "json",
+    "url": "https://cloudflare-protected-site.com",
+    "zone": "web_unlocker1"
+  }
+]
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Discloses rotation, anti-bot bypass, CAPTCHA solving, synchronous call taking 10-30 seconds, truncation for large pages, and pay-per-request pricing. All beyond annotations, no contradiction.

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?

Single paragraph with front-loaded purpose. Every sentence adds value: features, behavior, prerequisites, pricing, example. No redundant or vague sentences.

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?

Covers purpose, behavior, prerequisites, pricing, and example. Lacks explicit error handling and detailed return structure (though format parameter controls this). Adequate but not exhaustive.

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 100% with parameter descriptions. Description adds context (e.g., zone auto-naming, API key source) and an example, providing moderate value beyond schema.

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?

Description clearly states 'Fetch any URL through Bright Data Web Unlocker' with specific verb and resource. Differentiates from sibling brightdata_serp by mentioning built for hardest-to-scrape sites (Cloudflare, PerimeterX, Akamai).

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?

Description indicates when to use (hard-to-scrape sites) and notes behavior (10-30 seconds sync, truncation), but does not explicitly mention when-not-to-use or contrast with siblings like brightdata_serp. Still provides clear context.

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

All Bright Data toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation2/5

The ask_pipeworx family (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research) has significant boundary overlap, and ask_pipeworx_beta is explicitly identical to ask_pipeworx today. The six polymarket_* tools plus bet_research also cover heavily overlapping prediction-market territory, so an agent could easily route a query to the wrong one despite detailed descriptions.

Naming Consistency4/5

Most tools follow a consistent snake_case verb_noun pattern (ask_pipeworx, compare_entities, generate_llms_txt, list_subscriptions, validate_claim, scan_dependency). Minor deviations exist — entity_profile is noun-noun, brightdata_serp/brightdata_unlock use a vendor prefix, and remember/recall/forget are bare verbs — but the overall style is predictable and readable.

Tool Count2/5

At 33 tools this exceeds the 25+ threshold that signals an over-heavy surface. While the server covers multiple domains (data lookup, prediction markets, memory, subscriptions, AI visibility), many of those domains carry redundant variants that could be consolidated, making the count feel bloated rather than well-scoped.

Completeness4/5

The surface covers the core workflows well: querying (ask_pipeworx variants), deep research, entity resolution, entity profiles, comparisons, change feeds, claim verification, discovery/onboarding, subscriptions (list/subscribe/unsubscribe), memory (remember/recall/forget), and feedback. Minor gaps exist — there is no direct tool to fetch a returned pipeworx:// citation URI, and memory lacks an explicit update operation — but agents can work around these.

Resources