mcp-livedatapro

scrapeUrlToMarkdown

Bypass Cloudflare/anti-bot protection, render JavaScript, and extract clean LLM-ready Markdown from any URL. Use when extracting clean, LLM-ready Markdown text and outbound links from any public webpage URL, including JavaScript SPAs protected by anti-bot walls. Do not use for structured Amazon product pricing (use getEcommercePricing) or WHOIS domain ownership (use getDomainWhois). Executes headless browser rendering and strips ads/navigation.

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": {
      "target_url": "<target_url>"
    },
    "name": "scrapeUrlToMarkdown"
  }
}

Input Schema

Name	Required	Description	Default
`target_url`	Yes	Full HTTP/HTTPS URL of the public webpage to render and convert to clean Markdown.
`wait_for_js`	No	Whether to wait for dynamic SPA/React JavaScript execution before DOM extraction (defaults to true).

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 24, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / target_url / examples
```
Added value: +[
+  "https://example.com/pricing"
+]
```
- addedInput schema / properties / target_url / format
```
Added value: +"uri"
```
- addedInput schema / properties / target_url / pattern
```
Added value: +"^https?://.+"
```
- addedInput schema / properties / wait_for_js / default
```
Added value: +true
```
- addedInput schema / properties / wait_for_js / examples
```
Added value: +[
+  true
+]
```

Changed2 schema fields changedOct 24, 2026

changedInput schema / properties / target_url / description

Previous value: -"Full URL of the webpage to scrape and convert"New value: +"Full HTTP/HTTPS URL of the public webpage to render and convert to clean Markdown."

changedInput schema / properties / wait_for_js / description

Previous value: -"Wait for dynamic SPA/React content to render before extraction"New value: +"Whether to wait for dynamic SPA/React JavaScript execution before DOM extraction (defaults to true)."

First observedOct 21, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations provided, the description carries the full behavioral burden and does disclose key traits: headless browser execution, anti-bot bypass, JavaScript rendering, and that ads/navigation are stripped. It does not cover failure modes (what happens when the anti-bot wall wins), latency, page-size limits, or auth/privacy expectations, which leaves a noticeable gap for a network-scraping tool.

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?

The capability is front-loaded in the first sentence and the exclusions are clearly placed. The second sentence partially repeats 'clean, LLM-ready Markdown' from the first, which is mild waste, but the description stays short and scannable.

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?

There is no output schema, so the description usefully states the return shape (clean Markdown plus outbound links). For a two-parameter scraper that is nearly complete; what is missing is any statement about limits, timeouts, or behavior on render failure.

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 coverage is 100%, so both target_url and wait_for_js are already fully documented with types, defaults, formats, and examples. The description's reference to JavaScript SPAs implicitly connects to wait_for_js but adds no syntax or behavioral detail beyond the schema, so the 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?

The description names a specific verb and resource: rendering a URL and extracting clean Markdown, plus links. It explicitly distinguishes itself from getEcommercePricing and getDomainWhois, so an agent can route correctly without opening the 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?

It states when to use it (public webpage URLs, JavaScript SPAs behind anti-bot walls) and when not to use it, naming the two sibling alternatives by name. Both the positive and negative routing conditions are explicit.

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

All mcp-livedatapro 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?