Skip to main content
Glama

Build a multi-page site

build_site

Compile a website into import-ready Elementor JSON files with a shared theme, optional header/footer, and site manifest for organized imports.

Instructions

Compile a whole site to import-ready Elementor JSON: one file per page, all sharing a theme and an optional header/footer (e.g. navbar/footer templates). Supports site-level globals for reusable widget definitions across all pages. Set format: "classic" at site level for flat settings output (recommended for maximum import compatibility), or per-page format to override. Writes a site-manifest.json alongside the pages.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteNoThe site: { title?, theme?, format? ("atomic"|"classic"), header?: nodes[], footer?: nodes[], pages: [{ title, fileName?, theme?, format?, tree: [...] }], globals? }.
dryRunNoValidate and compile without writing files.
outputDirNoDirectory to write into. Defaults to $ELEMENTOR_MCP_OUT or ./output.
designIntensityNoVisual richness: minimal (no motion), standard (tasteful entrance animations), premium (full motion + scroll effects + decorative backgrounds). Default: standard.
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that it writes multiple files (one per page plus site-manifest.json) and supports dry run validation. However, it does not mention whether it overwrites existing files, idempotency, or error handling.

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?

The description is two sentences with the main purpose front-loaded. The second sentence is relatively long but includes necessary details. It is concise enough for quick understanding.

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 no output schema and no annotations, the description covers the input parameters, output (multiple files + manifest), and key behaviors like dry run. It lacks explanation of return values or error scenarios but is otherwise complete.

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 100%, but the description adds meaning by explaining the structure of the site parameter (e.g., pages array with tree, globals) and the purpose of format choices ('classic' recommended for compatibility). This adds value beyond the raw schema.

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 whole site into import-ready Elementor JSON with one file per page, shared theme, and optional header/footer. This distinguishes it from sibling tools like build_page (single page) and build_popup (popup).

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 explains when to use the tool (building multi-page sites with shared elements) and mentions format options. It does not explicitly state when not to use or provide alternatives, but the context from sibling tools gives implicit guidance.

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