WaveXisMCP

wavexis_pdf

Read-onlyIdempotent

Generate a PDF document directly from any web page. Specify URL, paper size, margins, and orientation to create print-ready files.

Instructions

Generate a PDF document from a web page.

Use wavexis_screenshot for image capture, or wavexis_page_pdf when pixel-level control over paper size and margins is 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'), '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_pdf"
  }
}

Input Schema

Name	Required	Description	Default
`input`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed15 schema fields changedv1.6.24Jul 29, 2026
- addedInput schema / $defs / PDFInput / properties / backend / description
```
Added value: +"Backend: 'cdp', 'bidi', or 'auto'"
```
- addedInput schema / $defs / PDFInput / properties / backend / enum
```
Added value: +[
+  "cdp",
+  "bidi",
+  "auto"
+]
```
- addedInput schema / $defs / PDFInput / properties / headless / description
```
Added value: +"Run browser in headless mode"
```
- addedInput schema / $defs / PDFInput / properties / js / description
```
Added value: +"JavaScript to execute before the action"
```
- addedInput schema / $defs / PDFInput / properties / landscape / description
```
Added value: +"Use landscape orientation"
```
- addedInput schema / $defs / PDFInput / properties / margin / description
```
Added value: +"Page margin (e.g. '0.4in')"
```
- addedInput schema / $defs / PDFInput / properties / media / enum
```
Added value: +[
+  "print",
+  "screen"
+]
```
- addedInput schema / $defs / PDFInput / properties / no_header_footer / description
```
Added value: +"Exclude header and footer from PDF"
```
- addedInput schema / $defs / PDFInput / properties / output_path / description
```
Added value: +"File path to save the output. If omitted, a default path is used."
```
- addedInput schema / $defs / PDFInput / properties / paper / enum
```
Added value: +[
+  "a4",
+  "letter",
+  "legal",
+  "a3",
+  "a5"
+]
```
- addedInput schema / $defs / PDFInput / properties / session_id / description
```
Added value: +"Active session ID. If omitted, a stateless session is created for this call."
```
- addedInput schema / $defs / PDFInput / properties / url / description
```
Added value: +"URL to navigate to (required without session_id)"
```
- addedInput schema / $defs / PDFInput / properties / wait_timeout / description
```
Added value: +"Timeout in ms for wait conditions"
```
- addedInput schema / $defs / PDFInput / properties / wait_timeout / maximum
```
Added value: +300000
```
- addedInput schema / $defs / PDFInput / properties / wait_timeout / minimum
```
Added value: +1000
```
First observedv1.0.1Jul 7, 2026

TDQS

A3.8/5.0

Behavior1/5

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

The description contradicts annotations: annotations mark readOnlyHint=true and destructiveHint=false, but description reports side effects like writing to output_path, launching browser, and navigating. This is a clear 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?

The description is concise, well-structured with clear sections, no redundant text, and immediately states the purpose.

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?

Covers core behavior, side effects, and return format. Lacks session management context, but annotations and schema partially fill gaps.

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 description mentions key parameters (url, js, output_path) and their roles, but does not cover all parameters (e.g., media, paper, margin). Given schema description coverage is 0% (contradicted by actual schema), description partially compensates.

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 it generates a PDF from a web page, and distinguishes between 'wavexis_screenshot' and 'wavexis_page_pdf' for image capture or pixel-level control.

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 advises when to use alternatives ('wavexis_screenshot' for images, 'wavexis_page_pdf' for pixel-level control) and lists side effects, guiding appropriate usage.

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

Deploy Server