Skip to main content
Glama
elementor-mcp

elementor-mcp

by heaventree

Snapshot a page

elementor_create_snapshot

Creates a named snapshot of a page's current layout, giving you a labeled restore point before major restructuring.

Instructions

Take a named snapshot of a page's current layout. Worth doing before a large restructuring so you have one clearly labelled point to come back to.

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

Input Schema

NameRequiredDescriptionDefault
siteNoConfigured site name. Omit to use the default site.
labelNoWhy you are taking it.manual snapshot
postIdYesWordPress post ID of the Elementor page, post or template.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare the safety profile (readOnlyHint false, destructiveHint false, openWorldHint true), so the description only needs to add nuance. It adds a little by framing the tool as a precautionary, recoverable checkpoint, but says nothing about what gets stored, whether a duplicate label overwrites an earlier snapshot, or any limits on snapshot count.

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, action first and rationale second, with zero filler. Every clause carries information an agent can act on.

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?

For a three-parameter tool this is close to sufficient, but with no output schema the description should say what comes back (a snapshot identifier or label) since that is what an agent would need to later restore. The snapshot lifecycle and recoverability story is left implicit.

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 in the schema, including the label's purpose ("Why you are taking it") and the site default. The description reinforces the naming intent via "named" and "clearly labelled" but adds no format, uniqueness, or default behavior beyond the schema.

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?

"Take a named snapshot of a page's current layout" gives a specific verb (snapshot) and resource (page layout) with the naming behavior included, which separates it from the mutation siblings like elementor_update_page_meta or elementor_replace_page_tree. It stops short of naming elementor_restore_snapshot as its counterpart, so the pairing must be inferred from 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?

The second sentence gives a clear triggering condition: use it before a large restructuring to preserve a labelled return point. There is no explicit exclusion or named alternative (e.g., that elementor_restore_snapshot is what you use to return to the snapshot), so an agent gets context but not full routing guidance.

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