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

wp-mcp-control-server

by mpierre135
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

wp_elementor_clear_page

Clear all Elementor sections and containers from a page to start a rebuild, leaving theme header/footer intact. Requires confirmation when safe mode is enabled.

Instructions

Remove all Elementor canvas sections/containers from a page for rebuilds. Theme builder header/footer templates are unaffected. 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>"
    },
    "name": "wp_elementor_clear_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNo
page_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.3.0

TDQS

A3.9/5.0
Behavior3/5

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

The description discloses a destructive action ('remove all sections/containers'), which is essential behavioral context. It also mentions the confirm:true requirement under safe mode. However, with no annotations, it leaves scope gaps: no mention of page_id validation, whether content is recoverable, or what happens if the page has no Elementor data.

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 sentences with no fluff. The core action and scope are front-loaded, and the safety requirement is stated compactly at the end.

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

Completeness3/5

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

Given no annotations and no output schema, the description covers the destructive nature and the confirm requirement, which are the most critical facts. It is slightly thin on safe-mode behavior, prerequisites for the tool to work, and what happens to Elementor data from theme templates, but the core call guidance is present.

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 0%, so the description must compensate, and it partially does: it explains the confirm parameter's role ('confirm:true required when safe mode is on'). However, it does not explain semantics of page_id beyond the schema's name, or whether confirm must also be true when safe mode is off.

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 states a specific verb ('remove'), a resource ('Elementor canvas sections/containers'), and the intent ('for rebuilds'). It explicitly distinguishes what is unaffected ('theme builder header/footer templates'), which separates it from the broader Elementor toolset.

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 clearly communicates when to use it: when clearing a page's Elementor canvas for a rebuild. It doesn't explicitly name sibling alternatives or when-not-to-use conditions, but the 'Theme builder header/footer templates are unaffected' line provides useful exclusion context.

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