Skip to main content
Glama
elementor-mcp

elementor-mcp

by heaventree

Create a page

elementor_create_page

Creates a new Elementor-enabled page, post, or template as a draft, optionally accepting an element tree and a canvas template for full-width layouts.

Instructions

Create a new Elementor-enabled page, post or template. Starts empty unless you pass an element tree. Created as a draft by default so nothing goes live unreviewed. For a full-width blank canvas set pageTemplate to elementor_canvas.

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": {
      "title": "<title>"
    },
    "name": "elementor_create_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteNoConfigured site name. Omit to use the default site.
slugNo
typeNoPost type, e.g. page or post.page
titleYesPage title.
parentNoParent post ID for hierarchical types.
statusNoPost status. Defaults to draft.draft
elementsNoOptional starting element tree.
pageTemplateNoTheme template: elementor_canvas (blank), elementor_header_footer (no theme content), or a theme file.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, open-world write, so the safety profile is covered. The description adds genuinely useful state behavior beyond that: the created object begins empty, defaults to draft so nothing is published unreviewed, and pageTemplate changes layout treatment. It does not mention permission/auth requirements or what happens on title collisions.

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 the core action, then default behavior, then a specific template tip. No filler or restatement of the title.

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, yet the description never says what creation returns (presumably the new page ID) — the single most important thing an agent needs to chain a follow-up edit. Otherwise it covers the default-state behavior and template option adequately for an 8-parameter creation tool.

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 88%, so the schema already documents site, status, type, parent, elements, and pageTemplate; baseline is 3. The description contributes some meaning beyond the schema by implying 'template' as an acceptable type value and tying elements to whether the page starts empty, but it says nothing about slug or parent 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 set ('Create a new Elementor-enabled page, post or template'), which immediately separates it from mutation siblings like elementor_add_container, elementor_replace_page_tree, or elementor_apply_template that modify existing content. An agent can tell this is the entry point for new content without opening the 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?

Gives concrete conditional guidance: content starts empty unless an element tree is passed, drafts are the default, and elementor_canvas is prescribed for a blank full-width canvas. It stops short of naming alternatives (e.g., apply a template afterward, or use add_container/add_widget to build content), so it is clear context without explicit exclusions.

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