Skip to main content
Glama
elementor-mcp

elementor-mcp

by heaventree

Delete a page

elementor_delete_page
Destructive

Move an Elementor page to trash or permanently delete it using its post ID; permanent removal requires force, site opt-in for destructive operations, and confirmation.

Instructions

Move a page to the trash, or delete it permanently with force. Permanent deletion additionally requires the site to have opted into destructive operations and confirm to be true.

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>"
    },
    "name": "elementor_delete_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteNoConfigured site name. Omit to use the default site.
forceNoSkip the trash and delete permanently. Cannot be undone.
postIdYesWordPress post ID of the Elementor page, post or template.
confirmNoRequired when force is true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known; the description adds the non-obvious facts that the default is recoverable trash, that force is irreversible, and that a separate site-level opt-in plus confirm=true are required. It does not say what happens when the opt-in is missing (error vs. silent downgrade) or how a trashed page can be recovered.

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 sentences, no filler, with the default (recoverable) behavior front-loaded before the destructive variant and its preconditions. Every sentence carries decision-relevant information.

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 4-parameter destructive tool with full schema coverage and annotations, the description covers the important pieces: mode selection, irreversibility, and the opt-in/confirm gate. The one gap is scope: the schema says postId targets a page, post, or template, while the description speaks only of 'pages', leaving ambiguity about templates.

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 description coverage is 100%, so force ('skip the trash and delete permanently, cannot be undone') and confirm ('required when force is true') are already documented in the schema. The description restates the same relationships without adding format, coupling, or failure-mode detail beyond the schema, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Move a page to the trash, or delete it permanently'), and crucially splits the operation into two modes (soft trash vs. permanent delete via force). It does not differentiate from the sibling elementor_delete_element, so an agent must infer the page-vs-element boundary from the tool names alone.

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?

It gives clear mode-selection guidance: default behavior is trash, and permanent deletion is opt-in via force. It also states the precondition for the destructive path (site must have opted into destructive operations, and confirm must be true), which is the key gating condition an agent needs. It stops short of naming alternatives such as restoring a trashed page or deleting elements.

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