Wafle-Scraper

scrape_browser

Extract text from web pages by navigating an isolated incognito browser, with rate limiting and ethical CAPTCHA handling for safe scraping.

Instructions

Navigate a page in an isolated incognito browser and extract text.

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": "scrape_browser"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes
`scroll`	No
`wait_selector`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 5, 2026

TDQS

C2.6/5.0

Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It mentions 'isolated incognito browser' implying privacy, but does not explain JavaScript handling, error behavior, or return format. The output schema exists but is not referenced.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence of 9 words, front-loaded with the core action. However, given the tool's complexity (3 parameters, output schema), it is too brief to be fully informative, balancing conciseness with substance.

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

Completeness2/5

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

The description does not cover parameter usage, output format, or behavioral details. With no annotations and low schema coverage, the description is insufficient for an agent to use the tool correctly without additional inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It does not explain the 'scroll' or 'wait_selector' parameters beyond their names, which are somewhat self-explanatory but lack context (e.g., scroll for dynamic loading, wait_selector for element visibility).

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 states 'Navigate a page in an isolated incognito browser and extract text,' which clearly identifies the tool's main action and resource. It distinguishes from siblings like 'browser_interact' (which likely involves interaction) and 'scrape_reddit' (site-specific), though the term 'extract text' could be more specific about scope.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives such as 'scrape_url' or 'browser_interact'. The description lacks any context about prerequisites, scenarios, or exclusions.

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

Deploy Server