Skip to main content
Glama
elementor-mcp

elementor-mcp

by heaventree

List page snapshots

elementor_list_snapshots
Read-onlyIdempotent

Lists layout snapshots stored for an Elementor page, newest first, including capture time and reason; one is saved automatically before each write.

Instructions

List the layout snapshots stored for a page, newest first, with when each was taken and why. One is taken automatically before every write this server makes.

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

Input Schema

NameRequiredDescriptionDefault
siteNoConfigured site name. Omit to use the default site.
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.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety is covered structurally. The description adds real value by disclosing return ordering, the per-entry 'when taken and why' payload, and the automatic pre-write creation policy. It says nothing about result volume, truncation, or what an empty list means, so it is helpful but not rich.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences, front-loaded with the verb and resource, then the return ordering and field list. The closing sentence about automatic snapshots earns its place as usage context rather than 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 read-only list tool with no output schema and fully-covered parameters, the description supplies what an agent needs: scope, ordering, and item contents. The only gap is absence of any statement about how many snapshots might come back or whether the list is ever truncated.

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%, with both site and postId documented including defaults and bounds, so the schema carries the load. The description only reinforces that the listing is scoped to a single page, adding no format or identifier details beyond the schema.

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?

States a specific verb (List) and resource (layout snapshots) scoped to a page, and adds the ordering (newest first) plus the fields each entry carries. It is readily distinguishable from elementor_create_snapshot and elementor_list_revisions without opening any schema.

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?

Explains the operating context that snapshots are created automatically before every write, which tells the agent when this tool is relevant and that it does not need to trigger snapshot creation first. It stops short of explicit when-not guidance or naming a sibling alternative to compare against.

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