Skip to main content
Glama
Sign In

scrapeunblocker-mcp-remote

by com.scrapeunblocker
OverviewDiscussionsAdmin

Fetch page HTML

fetch_html
Read-only

Fetch the fully rendered HTML of any web page through the ScrapeUnblocker API (https://docs.scrapeunblocker.com), bypassing anti-bot protection (Cloudflare, DataDome, PerimeterX, Akamai, Shape). Use when a normal fetch is blocked (403/429, captcha) or the page needs a real browser. Returns raw HTML. To read or summarise a page, fetch_markdown is much smaller. To click, type or scroll before capture, use browse_page.

Input Schema

NameRequiredDescriptionDefault
urlYesThe absolute URL to fetch (http/https).
wait_valueNoThe selector/expression paired with wait_method.
wait_methodNoOptional render-wait: 'css' selector or 'js' expression.
proxy_countryNoOptional ISO country code to route through, e.g. 'US'.
sleep_secondsNoExtra seconds to wait after load.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Changed1 schema field changed
    • removedInput schema / properties / steps
      Removed value: -{
-  "description": "Ordered browser actions to run in a real browser after the page loads (wait_for, wait_for_text, wait, click, type [human-like], select, press_key, scroll), then return the resulting HTML. NON-IDEMPOTENT: it runs once and is not retried. A failed step returns a 422 naming the offending step plus the page HTML at that point. Discover selectors with list_elements first.",
-  "items": {
-    "additionalProperties": false,
-    "properties": {
-      "action": {
-        "description": "The action to perform.",
-        "enum": [
-          "wait_for",
-          "wait_for_text",
-          "wait",
-          "click",
-          "type",
-          "select",
-          "press_key",
-          "scroll"
-        ],
-        "type": "string"
-      },
-      "clear": {
-        "description": "For 'type': clear the field first.",
-        "type": "boolean"
-      },
-      "selector": {
-        "description": "CSS selector the action targets (required for wait_for/click/type/select).",
-        "type": "string"
-      },
-      "selector_type": {
-        "description": "How to interpret `selector` (default 'css').",
-        "enum": [
-          "css",
-          "xPath",
-          "className",
-          "tagName"
-        ],
-        "type": "string"
-      },
-      "timeout_ms": {
-        "description": "Per-step timeout override in ms.",
-        "exclusiveMinimum": 0,
-        "type": "integer"
-      },
-      "value": {
-        "description": "Action payload: text to type/select, text for wait_for_text, a key name for press_key (e.g. 'Enter'), milliseconds for wait, or 'bottom'/pixels for scroll.",
-        "type": [
-          "string",
-          "number"
-        ]
-      }
-    },
-    "required": [
-      "action"
-    ],
-    "type": "object"
-  },
-  "type": "array"
-}
  3. Changed1 schema field changed
    • addedInput schema / properties / steps
      Added value: +{
+  "description": "Ordered browser actions to run in a real browser after the page loads (wait_for, wait_for_text, wait, click, type [human-like], select, press_key, scroll), then return the resulting HTML. NON-IDEMPOTENT: it runs once and is not retried. A failed step returns a 422 naming the offending step plus the page HTML at that point. Discover selectors with list_elements first.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "action": {
+        "description": "The action to perform.",
+        "enum": [
+          "wait_for",
+          "wait_for_text",
+          "wait",
+          "click",
+          "type",
+          "select",
+          "press_key",
+          "scroll"
+        ],
+        "type": "string"
+      },
+      "clear": {
+        "description": "For 'type': clear the field first.",
+        "type": "boolean"
+      },
+      "selector": {
+        "description": "CSS selector the action targets (required for wait_for/click/type/select).",
+        "type": "string"
+      },
+      "selector_type": {
+        "description": "How to interpret `selector` (default 'css').",
+        "enum": [
+          "css",
+          "xPath",
+          "className",
+          "tagName"
+        ],
+        "type": "string"
+      },
+      "timeout_ms": {
+        "description": "Per-step timeout override in ms.",
+        "exclusiveMinimum": 0,
+        "type": "integer"
+      },
+      "value": {
+        "description": "Action payload: text to type/select, text for wait_for_text, a key name for press_key (e.g. 'Enter'), milliseconds for wait, or 'bottom'/pixels for scroll.",
+        "type": [
+          "string",
+          "number"
+        ]
+      }
+    },
+    "required": [
+      "action"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
  4. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, and the description adds genuinely new context: the request goes through a third-party anti-bot bypass service (Cloudflare, DataDome, PerimeterX, Akamai, Shape) and returns raw, unstripped HTML. It stops short of disclosing latency, rate limits, cost, or payload size, which matter for a browser-rendering proxy call.

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?

Four short sentences, front-loaded with what it does, then when to use it, then the return type, then the two alternatives. Every clause carries routing or behavioral information; no filler.

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?

Five parameters, all fully documented in the schema, no output schema needed because the description states 'Returns raw HTML'. Combined with annotations and explicit sibling routing, an agent has everything required to choose and invoke it correctly.

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%, so url, wait_method/wait_value, proxy_country and sleep_seconds are already documented in structured data. The description adds no meaning beyond that – notably it never mentions the render-wait or geo-routing options, so it neither compensates nor detracts; baseline 3 applies.

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 ('Fetch the fully rendered HTML of any web page'), names the provider (ScrapeUnblocker), and explicitly contrasts itself with fetch_markdown and browse_page, so an agent can separate it from siblings without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Gives an explicit when-to-use trigger ('when a normal fetch is blocked (403/429, captcha) or the page needs a real browser') and routes two adjacent cases to named alternatives: fetch_markdown for reading/summarising and browse_page for interaction.

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

All scrapeunblocker-mcp-remote toolsInspect
Try in Browser
Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources