Skip to main content
Glama
Sign In

Frontman for WordPress

by io.github.frontman-ai
OverviewDiscussionsAdmin

wp_elementor_save_page_data

Destructive

Replaces the full Elementor element tree for a post after saving the previous tree as a private rollback snapshot. Ask the user for confirmation first and only call with confirm=true after approval. Use granular element tools when possible; call wp_elementor_flush_css after visual changes. Do not pass partial data like [{}]; data must be the complete Elementor tree returned by wp_elementor_get_page_data with targeted edits applied.

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": {
      "site_id": "<site_id>",
      "post_id": "<post_id>",
      "data": "<data>",
      "confirm": "<confirm>"
    },
    "name": "wp_elementor_save_page_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYesFull Elementor element tree.
confirmYesMust be true only after the user explicitly confirms replacing the full Elementor page data.
post_idYes
site_idYesThe connected site's id returned by list_sites. Call list_sites first; do not use a URL or WordPress post ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and non-idempotent, but the description adds the crucial mitigating behavior: the previous tree is saved as a private rollback snapshot before replacement, and confirm must be true only after explicit user approval. That is exactly the operational and safety context an agent needs before invoking a destructive full-overwrite.

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?

Front-loaded with the core action and its safeguard, then dependencies and constraints. Four sentences with no filler, though the final constraint sentence is dense and could be split for faster scanning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers replacement semantics, rollback safety, confirmation gating, the prerequisite read tool, and the required follow-up CSS flush – everything needed for a destructive, no-output-schema mutation tool. Nothing an agent needs in order to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 75%, and the description adds real meaning to the two least self-explanatory parameters: confirm gated on explicit user approval, and data constrained to the complete tree from wp_elementor_get_page_data with targeted edits, not a partial array. site_id and post_id are left to the schema, which already documents them adequately.

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 – 'Replaces the full Elementor element tree for a post' – and immediately distinguishes itself from the granular element tools by scoping the operation to a full-tree replacement. An agent can tell this apart from wp_elementor_update_element 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 Guidelines5/5

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

Gives explicit when-to-use and when-not-to-use guidance: use granular element tools when possible, call this only after user confirmation, and call wp_elementor_flush_css after visual changes. It also names a precondition (data must originate from wp_elementor_get_page_data) and a prohibition (no partial data like [{}]).

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

All Frontman for WordPress toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources