Skip to main content
Glama
elementor-mcp

elementor-mcp

by heaventree

Call an Elementor native MCP ability

elementor_native_mcp_call

Invoke Elementor's native MCP abilities through the bridge to use v4 atomic features such as global classes, variables, and components. Confirm the module is active via site status first.

Instructions

Invoke one of Elementor's own built-in MCP abilities through the bridge. Elementor 4.3+ ships abilities covering v4 atomic features (global classes, variables, components, compositions) that have no v3 equivalent. Only works where that module is active — check elementor_site_status first, under nativeMcp.

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": {
      "tool": "<tool>"
    },
    "name": "elementor_native_mcp_call"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteNoConfigured site name. Omit to use the default site.
toolYesThe native ability slug, e.g. "list-components".
inputNoArguments for that ability.

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 only declare openWorldHint=true, so the description carries most of the disclosure burden. It usefully adds the version gate, the module-active condition, and the discovery pointer to elementor_site_status/nativeMcp, but it never states whether the invoked ability may mutate site state, nor what happens on an unknown slug or failing ability. For a pass-through dispatcher whose behavior depends entirely on the target ability, that is a real gap.

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?

Three short sentences, front-loaded with what the tool does, followed by why it exists and then the operational precondition. No filler, and the gating information is placed before the agent would commit to a call.

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?

There is no output schema, and for a generic dispatcher the agent still lacks guidance on how to discover valid ability slugs or interpret the pass-through result. Version and activation conditions are covered well, but the discoverability gap and unstated mutation/error behavior leave this short of complete for a tool with a nested free-form input.

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%, so all three parameters (site, tool, input) are already documented, including the 'list-components' slug example. The description adds no format, naming convention, or validation detail for the free-form 'input' object beyond what the schema says. Baseline 3 applies when the schema does the work.

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?

The description states a specific verb and resource: invoking Elementor's built-in MCP abilities through a bridge, and scopes them to v4 atomic features (global classes, variables, components, compositions) with no v3 equivalent. That scope statement carves out territory from the wrapper siblings, though it does not explicitly distinguish against overlapping siblings such as elementor_get_global_classes.

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?

It gives an explicit prerequisite and pre-flight step: the native module must be active, and the agent should check elementor_site_status under nativeMcp first, with a version floor of 4.3+. It does not say when to prefer a wrapper tool over dispatching a native ability when both could serve the request.

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