WaveXisMCP

wavexis_screenshot

Read-onlyIdempotent

Capture a screenshot of a web page or matched element, with controls for full page, viewport size, image format, and output file.

Instructions

Capture a screenshot of a web page or matched element.

Use wavexis_pdf when a print-ready document is needed, or wavexis_annotated_screenshot when labelled element markers are required.

Side effects: launches/acquires a browser backend, navigates to url if provided, optionally evaluates js; writes to output_path when given. Returns: JSON string with keys: 'status' ('ok'/'error'), 'format' (str), 'base64' (str) or 'path' (str), 'size_bytes' (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_screenshot"
  }
}

Input Schema

Name	Required	Description	Default
`input`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedv1.6.24Jul 29, 2026
- addedInput schema / $defs / ScreenshotInput / properties / backend / description
```
Added value: +"Backend: 'cdp', 'bidi', or 'auto'"
```
- addedInput schema / $defs / ScreenshotInput / properties / backend / enum
```
Added value: +[
+  "cdp",
+  "bidi",
+  "auto"
+]
```
- addedInput schema / $defs / ScreenshotInput / properties / format / enum
```
Added value: +[
+  "png",
+  "jpeg"
+]
```
- addedInput schema / $defs / ScreenshotInput / properties / headless / description
```
Added value: +"Run browser in headless mode"
```
- addedInput schema / $defs / ScreenshotInput / properties / height / description
```
Added value: +"Viewport height in pixels"
```
- addedInput schema / $defs / ScreenshotInput / properties / session_id / description
```
Added value: +"Active session ID. If omitted, a stateless session is created for this call."
```
- addedInput schema / $defs / ScreenshotInput / properties / wait_selector / description
```
Added value: +"CSS selector to wait for (used when wait_strategy='selector')"
```
- addedInput schema / $defs / ScreenshotInput / properties / wait_strategy / description
```
Added value: +"Wait strategy: load, domcontentloaded, networkidle, selector, url, none"
```
- addedInput schema / $defs / ScreenshotInput / properties / wait_strategy / enum
```
Added value: +[
+  "load",
+  "domcontentloaded",
+  "networkidle",
+  "selector",
+  "url",
+  "none"
+]
```
- addedInput schema / $defs / ScreenshotInput / properties / wait_timeout / description
```
Added value: +"Timeout in ms for wait conditions"
```
- addedInput schema / $defs / ScreenshotInput / properties / width / description
```
Added value: +"Viewport width in pixels"
```
First observedv1.0.1Jul 7, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Description discloses side effects (launches browser, navigates, evaluates JS, writes to disk) beyond annotations. Annotations already indicate readOnlyHint=true, idempotentHint=true, destructiveHint=false, and description adds specifics. Return format is also described. No contradiction.

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?

Description is extremely concise—three short paragraphs covering purpose, alternatives, side effects, and return format. No wasted words, front-loaded with core purpose.

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?

Given the tool's complexity (many parameters, many sibling tools), the description provides complete context: purpose, usage guidelines, side effects, return structure. Output schema exists, so return values need not be detailed further.

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?

The input schema has comprehensive descriptions for all properties, so the description does not add additional meaning. Schema coverage is 0% per context, but the actual schema includes parameter descriptions. Leading to baseline 3.

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?

Description clearly states the tool captures a screenshot of a web page or matched element. It distinguishes from sibling tools wavexis_pdf (print-ready document) and wavexis_annotated_screenshot (labelled element markers). Verb and resource are specific.

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 provides when to use alternatives: 'Use wavexis_pdf when a print-ready document is needed, or wavexis_annotated_screenshot when labelled element markers are required.' Also lists side effects, which helps the agent decide context.

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

Deploy Server