Skip to main content
Glama

Build Elementor popup

build_popup

Build import-ready Elementor v4 popup JSON with configurable triggers, entrance/exit animations, and timing rules.

Instructions

Compile a popup blueprint into import-ready Elementor v4 JSON with popup triggers, entrance/exit animations, and timing rules in page_settings. Use type: 'popup' with a popup config. The popup content goes in the tree.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
treeNoContent tree for the popup body (same blueprint nodes as pages).
themeNoTheme object from generate_theme.
titleYesPopup title (shown in Elementor).
timingNoArray of { type: 'times'|'days'|'sessions'|'devices', settings: {...} }. E.g. times: { count: 1, period: 'session' }.
fileNameNoOutput file name (without extension).
triggersNoArray of { type: 'page_load'|'scrolling'|'click'|'exit_intent', settings?: {...} }. E.g. scrolling needs { offset: 25 }, click needs { selector: '.my-trigger' }.
outputDirNoDirectory to write into. Defaults to $ELEMENTOR_MCP_OUT or ./output.
exitAnimationNoExit animation name, e.g. 'fadeOut'.
entranceAnimationNoEntrance animation name, e.g. 'fadeIn', 'slideInDown'.
Behavior3/5

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

No annotations are provided, so the description carries full burden. It explains the output (import-ready JSON) and mentions page_settings includes triggers/animations/timing, but it does not disclose side effects like file writing (outputDir parameter) or any destructive actions. The description is adequate but missing some behavioral details.

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?

The description is two concise sentences that are front-loaded with the core purpose. Every word adds value, with no redundancy or fluff.

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?

Given 9 parameters and no output schema, the description covers the high-level purpose and structure. It does not explain prerequisites (e.g., generate_theme for theme) or the return value, but it is largely complete for understanding the tool's role in a popup-building workflow.

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 description coverage is 100%, so baseline is 3. The description adds context by stating the overall structure (popup config, content in tree) and references triggers/animations/timing in page_settings, which provides meaning beyond individual parameter descriptions.

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?

The description clearly states the tool compiles a popup blueprint into Elementor v4 JSON with specific features like triggers, animations, and timing rules. It distinguishes from sibling tools like build_page and build_site by specifying it's for popups, not pages or sites.

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 description mentions 'Use type: popup with a popup config,' which implies when to use the tool (for popups). However, it does not explicitly state when not to use it or mention alternatives like build_page for pages.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Smecha10/elementor-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server