Skip to main content
Glama
elementor-mcp

elementor-mcp

by heaventree

Delete an element

elementor_delete_element
Destructive

Removes a specified Elementor element and all nested content from a page. Creates a snapshot first so the deletion can be undone.

Instructions

Remove an element and everything inside it from a page. A snapshot is taken first, so elementor_restore_snapshot can undo it.

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": {
      "postId": "<postId>",
      "elementId": "<elementId>"
    },
    "name": "elementor_delete_element"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteNoConfigured site name. Omit to use the default site.
postIdYesWordPress post ID of the Elementor page, post or template.
elementIdYesElementor element id, as returned by elementor_get_outline.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the bar is lower. The description adds two non-obvious traits not in the annotations: the deletion is recursive ('everything inside it') and a snapshot is captured beforehand, making the operation recoverable via elementor_restore_snapshot.

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?

Two short sentences with zero filler; the destructive scope is front-loaded and the undo mechanism follows immediately.

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?

For a destructive three-parameter tool with no output schema, the definition covers what is destroyed (children included) and how to recover. Minor omissions remain, such as behavior on an invalid elementId or whether the snapshot is site-scoped, but nothing essential to calling it correctly is missing.

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 coverage is 100%, so postId, elementId and site are already fully documented, including the pointer to elementor_get_outline for obtaining elementId. The description adds nothing about parameter formats or edge cases, so the baseline 3 applies.

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?

States a specific verb and resource ('Remove an element') plus the critical scope note 'and everything inside it from a page', which immediately distinguishes it from elementor_delete_page and from non-destructive siblings like elementor_move_element or elementor_wrap_element.

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

Usage Guidelines4/5

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

The use case is clear (removing an element) and it explicitly routes the agent to elementor_restore_snapshot as the recovery path, which is a usable alternative. It stops short of explicit when-not guidance, e.g. that re-parenting children via move/wrap is preferable if the content should be preserved.

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