Skip to main content
Glama
elementor-mcp

elementor-mcp

by heaventree

Restore a WordPress revision

elementor_restore_revision
Destructive

Restore an Elementor page layout from a WordPress revision that carries Elementor data, capturing a snapshot first so the current state can be recovered.

Instructions

Restore a page's Elementor layout from a WordPress revision. Only works on revisions flagged as carrying Elementor data. A snapshot is taken first.

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

Input Schema

NameRequiredDescriptionDefault
siteNoConfigured site name. Omit to use the default site.
postIdYesWordPress post ID of the Elementor page, post or template.
revisionIdYesRevision id from elementor_list_revisions.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.8/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, but the description adds genuinely new behavior: a snapshot is taken before the restore, which tells the agent the operation is recoverable. It also discloses the revision eligibility constraint. It does not say what happens to the current layout if snapshot creation fails or how long the snapshot is retained.

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 compact sentences with zero filler, and the scope statement is front-loaded before the eligibility constraint and the safety note. Nothing is repeated from the title.

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 mutation with full schema coverage and no output schema, the definition covers scope, precondition, and the safety net that matters most to an agent deciding whether to call it. Only the failure-mode behavior is left unstated.

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 all three parameters are already documented, including that revisionId comes from elementor_list_revisions. The description reinforces the revision validity requirement but adds no syntax or format detail beyond the schema; baseline 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 ('Restore a page's Elementor layout from a WordPress revision'), which is clearly distinguishable from the snapshot-based sibling. It stops short of naming elementor_restore_snapshot as the alternative path, so the differentiation is implied rather than explicit.

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

Usage Guidelines3/5

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

It gives one useful precondition — the revision must be flagged as carrying Elementor data — and the schema points to elementor_list_revisions for obtaining an id. There is no explicit statement about when to prefer this over elementor_restore_snapshot or what to do when the precondition fails.

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