Skip to main content
Glama
elementor-mcp

elementor-mcp

by heaventree

Undo: restore a page snapshot

elementor_restore_snapshot
Destructive

Restore an Elementor page to a saved snapshot, or omit the snapshot ID to undo the most recent change; the current state is saved first so the rollback is reversible.

Instructions

Roll a page back to a snapshot. With no snapshotId this restores the most recent one, which undoes the last change made through this server. The current state is snapshotted first, so a restore is itself reversible.

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_restore_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteNoConfigured site name. Omit to use the default site.
postIdYesWordPress post ID of the Elementor page, post or template.
snapshotIdNoSnapshot to restore. Omit to undo the most recent change.

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 openWorldHint=true, so the safety profile is supplied. The description adds genuinely new behavioral context by disclosing that the current state is snapshotted first, making the restore itself reversible — material information that softens the destructive hint and an agent would not otherwise know. It does not cover permissions or how snapshots are created/listed.

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 short sentences, front-loaded with the action, then the default behavior, then the reversibility guarantee. Every sentence carries distinct information and there is no filler.

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, open-world mutation with no output schema, the description covers the action, the default path, and the reversibility safeguard — the essentials an agent needs to call it responsibly. The remaining gap is how to discover existing snapshot IDs, which the sibling elementor_create_snapshot presumably addresses but is never referenced.

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 all three parameters are already documented, including "Omit to undo the most recent change" for snapshotId. The description's default-behavior sentence largely restates that schema text and adds nothing about postId scoping or how to obtain valid snapshot IDs; 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?

"Roll a page back to a snapshot" gives a specific verb (roll back/restore) and resource (page snapshot), and the default-snapshot sentence clarifies the undo semantics. It does not, however, explicitly distinguish itself from the sibling elementor_restore_revision, which an agent could plausibly confuse with this one.

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 description states a clear usage context: with no snapshotId it undoes the last change made through this server, which is the primary intended use. It offers no when-not guidance and never mentions elementor_restore_revision as the alternative for revision-based rollback, so routing between the two remains implicit.

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