WaveXisMCP

wavexis_cookies_delete

DestructiveIdempotent

Deletes browser cookies that match a given name and domain, removing targeted stored data while leaving other cookies intact. Useful for clearing specific site sessions or fixing cookie-related issues.

Instructions

Delete cookies matching a name and domain in the browser.

Use wavexis_cookies_clear to remove all cookies, or wavexis_cookies_set to add a new cookie.

Side effects: launches/acquires a browser backend, navigates to url if provided, destructively removes matching cookies from browser state. Returns: JSON string with keys: 'status' ('ok'/'error').

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_cookies_delete"
  }
}

Input Schema

Name	Required	Description	Default
`input`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedv1.6.24Jul 29, 2026
- addedInput schema / $defs / CookiesDeleteInput / properties / backend / description
```
Added value: +"Backend: 'cdp', 'bidi', or 'auto'"
```
- addedInput schema / $defs / CookiesDeleteInput / properties / backend / enum
```
Added value: +[
+  "cdp",
+  "bidi",
+  "auto"
+]
```
- addedInput schema / $defs / CookiesDeleteInput / properties / domain / description
```
Added value: +"Cookie domain"
```
- addedInput schema / $defs / CookiesDeleteInput / properties / domain / minLength
```
Added value: +1
```
- addedInput schema / $defs / CookiesDeleteInput / properties / headless / description
```
Added value: +"Run browser in headless mode"
```
- addedInput schema / $defs / CookiesDeleteInput / properties / name / description
```
Added value: +"Name of the item"
```
- addedInput schema / $defs / CookiesDeleteInput / properties / name / minLength
```
Added value: +1
```
- addedInput schema / $defs / CookiesDeleteInput / properties / session_id / description
```
Added value: +"Active session ID. If omitted, a stateless session is created for this call."
```
- addedInput schema / $defs / CookiesDeleteInput / properties / url / description
```
Added value: +"URL to navigate to (required without session_id)"
```
- addedInput schema / $defs / CookiesDeleteInput / properties / wait_timeout / description
```
Added value: +"Timeout in ms for wait conditions"
```
- addedInput schema / $defs / CookiesDeleteInput / properties / wait_timeout / maximum
```
Added value: +300000
```
- addedInput schema / $defs / CookiesDeleteInput / properties / wait_timeout / minimum
```
Added value: +1000
```
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?

Discloses side effects: launches/acquires browser backend, navigates if URL provided, destructively removes cookies. Annotations provide destructiveHint, but description adds valuable context about backend and navigation, fully aligning with annotations.

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?

Four sentences, front-loaded with purpose, then alternatives, side effects, and return. Every sentence earns its place with no redundancy.

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?

Comprehensive for a deletion tool: covers purpose, side effects, return format, and distinguishes from siblings. Output schema exists for return details, so no gap.

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 already describes all parameters (name, domain, etc.). The tool description adds no new semantic info beyond mentioning 'matching a name and domain', which is covered by schema. Baseline 3 is appropriate given schema descriptions exist.

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 the tool deletes cookies matching a name and domain, with specific verb and resource. It distinguishes from siblings like wavexis_cookies_clear and wavexis_cookies_set, making the purpose unambiguous.

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 tells when to use this tool vs alternatives: use wavexis_cookies_clear to remove all cookies, or wavexis_cookies_set to add. Provides clear context and exclusion guidance.

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

Deploy Server