Skip to main content
Glama

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. Pass steps to interact with the page (search, click, paginate) before capture - use the list_elements tool first to discover selectors.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe absolute URL to fetch (http/https).
stepsNoOrdered 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.
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
    • 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"
+}
  2. 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 and destructiveHint=false, so the safety profile is covered. The description adds behavioral context like bypassing anti-bot protection and using a real browser, which helps the agent understand what happens under the hood. It also notes that steps are non-idempotent in the schema, though not in the main description—still, it adds enough value beyond annotations.

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?

Two sentences, front-loaded with the core purpose and key differentiator (anti-bot bypass). The alternative-trigger guidance and list_elements hint are placed efficiently without redundancy. Every sentence earns its place.

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?

For a tool with a detailed schema and read-only annotations, the description covers the essential points: what it does, when to use it, what it returns, and how to prepare for interactive steps. No critical missing information for an agent to 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 each parameter is documented. The description adds a small amount of guidance for the steps parameter ('interact with the page... use the list_elements tool first'), but this is a usage hint rather than new semantic meaning. Baseline 3 is appropriate; the schema does the heavy lifting.

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?

Clearly states the specific action ('Fetch the fully rendered HTML of any web page') and resource (web page via ScrapeUnblocker API). It differentiates from siblings like fetch_parsed (raw vs parsed HTML) and google_search (search vs fetch). No ambiguity about what the tool does.

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?

Explicitly tells when to use: 'Use when a normal fetch is blocked (403/429, captcha) or the page needs a real browser.' It also directs the agent to use list_elements first for steps, providing clear alternative tool usage guidance.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources