WaveXisMCP

wavexis_scrape

Read-onlyIdempotent

Scrape structured data from multiple URLs by running a JavaScript expression on each page. Use it to collect results across paginated or multi-page sites, with offset, limit, and JSON or CSV output.

Instructions

Scrape data from multiple URLs by evaluating a JS expression on each.

Use wavexis_eval for single-page evaluation, or wavexis_scrape when the same expression must run across many pages with pagination.

Side effects: launches/acquires a browser backend, navigates to each URL in urls sequentially, evaluates expression in every page context. Returns: JSON string with keys: 'status' ('ok'/'error'), 'results' (list[dict[str, Any]]), 'format' (str), 'count' (int), 'total' (int).

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": {
      "input": "<input>"
    },
    "name": "wavexis_scrape"
  }
}

Input Schema

Name	Required	Description	Default
`input`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedv1.6.24Jul 29, 2026
- addedInput schema / $defs / ScrapeInput / properties / backend / description
```
Added value: +"Backend: 'cdp', 'bidi', or 'auto'"
```
- addedInput schema / $defs / ScrapeInput / properties / backend / enum
```
Added value: +[
+  "cdp",
+  "bidi",
+  "auto"
+]
```
- addedInput schema / $defs / ScrapeInput / properties / headless / description
```
Added value: +"Run browser in headless mode"
```
- addedInput schema / $defs / ScrapeInput / properties / output_format / enum
```
Added value: +[
+  "json",
+  "csv"
+]
```
- addedInput schema / $defs / ScrapeInput / properties / session_id / description
```
Added value: +"Active session ID. If omitted, a stateless session is created for this call."
```
- addedInput schema / $defs / ScrapeInput / properties / wait_timeout / description
```
Added value: +"Timeout in ms for wait conditions"
```
- addedInput schema / $defs / ScrapeInput / properties / wait_timeout / maximum
```
Added value: +300000
```
- addedInput schema / $defs / ScrapeInput / properties / wait_timeout / minimum
```
Added value: +1000
```
First observedv1.0.1Jul 7, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds beyond that: 'Side effects: launches/acquires a browser backend, navigates to each URL sequentially, evaluates expression in every page context.' It also describes the return JSON structure, providing useful behavioral context.

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?

The description is two paragraphs, first sentence defines purpose, second provides usage guidance and side effects. Every sentence adds value, no fluff. Well-structured and appropriately sized.

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?

Given the complexity (multiple URLs, browser backend) and rich input schema with 9 parameters, the description covers the overall behavior, return format, and side effects. It lacks explanation of some parameters like backend or selector, but those are described in the schema. It is mostly complete.

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 0% according to context, but actually the schema has descriptions for each parameter. The tool description does not add any additional parameter-level detail beyond what's already in the schema. Baseline is 3 due to schema coverage, and description adds no extra semantic value.

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 clearly states 'Scrape data from multiple URLs by evaluating a JS expression on each.' It uses specific verb (scrape) and resource (data from URLs), and distinguishes from sibling wavexis_eval by noting it's for single-page evaluation.

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

Usage Guidelines4/5

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

The description explicitly says when to use this tool vs wavexis_eval: 'Use wavexis_eval for single-page evaluation, or wavexis_scrape when the same expression must run across many pages with pagination.' It provides clear context but does not mention when not to use it beyond that.

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

Deploy Server