Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

WordPress: Wp elementor set

wordpress_specialist_wp_elementor_set
Destructive

Replaces a post's Elementor data tree while validating every node, enforcing the 5,000-node cap, and firing the after_save hook so caches and CSS rebuild. Use it to write Elementor layouts safely.

Instructions

[UNIFIED] Replace a post's _elementor_data tree. Companion validates every node has id/elType/settings, enforces the 5,000-node cap (S-14), writes via update_post_meta, and fires elementor/document/after_save so caches and CSS clear. Oversized payloads return elementor_too_large; switch to wp_elementor_template_apply. Requires Airano MCP Bridge v2.13.0+ and edit_post on the target.

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": "<site>",
      "post_id": "<post_id>",
      "data": "<data>"
    },
    "name": "wordpress_specialist_wp_elementor_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYes
siteYes
post_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses node-level validation (id/elType/settings), the 5,000-node cap and its error code, the exact write path (update_post_meta), the after_save hook that clears caches and CSS, and the required capability and bridge version. That is exactly the operational context an agent needs before destroying existing Elementor data.

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 in the first clause, then preconditions and the failure path. It is dense but every clause carries information; the bracketed [UNIFIED] tag and backticked error code add slight noise.

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, no-output mutation tool this covers validation, limits, side effects, version and permission prerequisites, and the fallback. It stops short of saying whether the previous tree is recoverable (revision/backup) and what the call returns on success.

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 0% and the `data` array has an empty item schema, so the description carries the load by defining the required node shape (id/elType/settings) and the size limit. `post_id` is implied as the target and `site` is never mentioned, leaving one gap.

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?

"Replace a post's _elementor_data tree" is a specific verb plus resource, and it is clearly distinguished from the read-side sibling wp_elementor_get and from wp_elementor_template_apply, which it explicitly routes oversized payloads to.

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?

Gives a concrete selection rule: payloads that exceed the 5,000-node cap return `elementor_too_large` and should switch to wp_elementor_template_apply. It also states the prerequisite (Airano MCP Bridge v2.13.0+ and edit_post on the target), but it does not contrast this tool with the rest of the elementor family in the normal, non-oversized case.

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

Deploy Server

Other Tools