WarpPay402 Gateway

This connector has been deprecated

I used the same url for two different postings.

browser_scraper

Read-only

Unblockable JS-rendering browser scraper ($0.005 USDC)

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": {
      "url": "<url>"
    },
    "name": "browser_scraper"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	Dynamic or protected website URL requiring headless browser rendering

Output Schema

Name	Required	Description
`title`	No	Rendered page title
`success`	Yes	Render success status
`markdown`	Yes	Chromium DOM rendered markdown content

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 25, 2026

addedInput schema / properties / url / description

Added value: +"Dynamic or protected website URL requiring headless browser rendering"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "markdown": {
+      "description": "Chromium DOM rendered markdown content",
+      "type": "string"
+    },
+    "success": {
+      "description": "Render success status",
+      "type": "boolean"
+    },
+    "title": {
+      "description": "Rendered page title",
+      "type": "string"
+    }
+  },
+  "required": [
+    "success",
+    "markdown"
+  ],
+  "type": "object"
+}

First observedSep 1, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true and idempotentHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral fact not in annotations: the per-call cost of $0.005 USDC, plus the 'unblockable' anti-bot claim. It says nothing about rate limits, latency, or failure modes.

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?

A single front-loaded clause with no filler; each element (unblockable, JS-rendering, price) carries information. It is arguably terse to the point of under-specification, but nothing is redundant.

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

Completeness3/5

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

An output schema exists, so return values need no explanation, and the single parameter is fully documented. What is missing is routing context against the many sibling retrieval tools and any note on blocking behavior, timeouts, or how the USDC charge is applied.

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?

There is only one parameter and schema description coverage is 100%, so the schema already explains that the url must point to a dynamic or protected site. The description adds no syntax or format detail about the URL beyond that, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb+resource ('browser scraper') and qualifies it with the differentiating traits 'JS-rendering' and 'unblockable', which separates it from plain 'web_scraper'. It does not, however, explicitly contrast itself with siblings like web_scraper or render_screenshot.

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?

Usage is only implied: 'JS-rendering' and the schema's 'Dynamic or protected website URL requiring headless browser rendering' suggest when this tool is needed over a static scraper, but the description never states when to use it versus web_scraper or render_screenshot.

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

All WarpPay402 Gateway tools Inspect

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

Need Help?