Skip to main content
Glama
elementor-mcp

elementor-mcp

by heaventree

List WordPress revisions

elementor_list_revisions
Read-onlyIdempotent

List a page's WordPress revisions and flag which ones actually carry Elementor layout data, so you can find older layout states beyond snapshots.

Instructions

List a page's WordPress revisions, flagging which of them actually carry Elementor layout data. Revisions reach further back than snapshots but are less reliable for Elementor content.

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

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

A4/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 the safety profile is covered. The description adds genuine value by disclosing that results include an Elementor-data flag and by warning about reliability relative to snapshots, but says nothing about pagination, limits, or how far back the list extends.

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 sentences, zero filler. The primary action is front-loaded and the caveat follows as supporting context rather than burying the purpose.

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 two-parameter read-only list tool with no output schema, the description covers what is returned (revisions annotated with Elementor layout presence) and a reliability caveat. The remaining gap is operational: no mention of result volume, ordering, or paging behavior.

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% for both parameters, including the site-default omission and the post ID constraint, so the schema carries the burden. The description only implies the postId scoping via 'a page's' and adds no new parameter semantics.

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 and resource (list a page's WordPress revisions) plus a distinguishing capability: flagging which revisions actually carry Elementor layout data. It also names the sibling category it competes with (snapshots), so an agent can tell the two apart without opening either 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?

The second sentence gives a usable selection heuristic - revisions go further back in history but are less reliable for Elementor content, implicitly steering toward snapshots when Elementor fidelity matters. It stops short of an explicit 'use X instead when...' instruction or any prerequisites (e.g. whether revisions must be enabled).

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