Skip to main content
Glama
Sign In
wp-mcp-control-server

wp-mcp-control-server

by mpierre135
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

wp_elementor_remove_element

Remove Elementor widgets, sections, or containers by element ID. Confirm when safe mode is on to complete removal.

Instructions

Remove a widget, section, or container by element ID. confirm:true required when safe mode is on.

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": {
      "page_id": "<page_id>",
      "element_id": "<element_id>"
    },
    "name": "wp_elementor_remove_element"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNo
page_idYes
element_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

Discloses a behavioral aspect (confirm requirement in safe mode), but lacks details on permanence, permissions, or side effects of removal. No annotations are provided, so the description carries the full burden.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely concise with only two short sentences, front-loading the key action and resource. No wasted words, but could be slightly more structured for clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given it is a destructive tool with three parameters and no output schema or annotations, the description lacks context on prerequisites, return values, error conditions, and the role of 'page_id'. The agent may struggle to use it correctly.

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 explains the role of 'element_id' and the 'confirm' parameter, but does not address 'page_id' at all. Since schema coverage is 0%, this leaves one parameter completely undocumented.

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 action ('Remove') and specifies the target resource ('a widget, section, or container by element ID'), distinguishing it from sibling tools like insert or clone.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives. The description only mentions a condition ('confirm:true required when safe mode is on') but does not differentiate from other Elementor manipulation tools.

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

Deploy Server

Other Tools