WaveXisMCP

wavexis_dom_remove

DestructiveIdempotent

Remove a DOM element using a CSS selector, permanently deleting it from the live page. Returns a status of 'ok' or 'error' to confirm success.

Instructions

Remove an element matching a CSS selector from the DOM.

Use wavexis_dom_set_attr to hide an element (e.g. display:none) instead of deleting it.

Side effects: Destructive; permanently removes the matched element from the live DOM. 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_dom_remove"
  }
}

Input Schema

Name	Required	Description	Default
`input`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv1.6.24Jul 29, 2026
- addedInput schema / $defs / DOMRemoveInput / properties / selector / description
```
Added value: +"CSS selector for the target element"
```
- addedInput schema / $defs / DOMRemoveInput / properties / selector / minLength
```
Added value: +1
```
- addedInput schema / $defs / DOMRemoveInput / properties / session_id / description
```
Added value: +"Active session ID from wavexis_session_open"
```
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?

Annotations indicate destructiveHint true; description adds 'permanently removes' and 'Destructive' side effects, plus return format. 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?

Three efficient sentences, front-loaded purpose, no redundant information.

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?

Covers purpose, alternative usage, side effects, and return format. Complete for a simple destructive DOM removal tool.

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 provides descriptions for both parameters (selector, session_id), so baseline 3. Description does not add extra semantics beyond the schema.

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?

Clearly states verb 'remove' and resource 'element matching CSS selector'. Distinguishes from sibling wavexis_dom_set_attr for hiding instead of deleting.

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 using wavexis_dom_set_attr for hiding instead of this tool, providing clear when-not-to-use guidance.

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

Deploy Server