The agent-native Elementor growth layer. Complete WordPress/Elementor AI platform with AI-native REST API, Theme Builder management, intelligent composition, workflow staging, and governance. Route preflight, route discovery, structural validation, and mass export included.
Elementeer exposes 16 tools with explicit REST route registration and JSON Schema parameter definitions. Naming follows verb_noun convention (list_, create_, get_, update_, delete_, toggle_). All tools have descriptions (avg 95 chars, within 10-1024 range). Parameter schemas are present with types and enums. However, output schemas are NOT documented, the code shows parameter validation but no response structure definitions. Error handling is absent from visible code. Several tools lack parameter descriptions (e.g., update_template has no description of what fields can be updated). Tool composition is reasonable but some tools conflate concerns (get_assessment returns 10+ different data types in one call).
Create a new Elementor template with title, type, status, elementor data, categories, and tags
Delete a template by ID
Duplicate an existing template
Get details for a specific add-on by plugin slug
Get list of capabilities for a specific add-on
Get list of post types supported by a specific add-on
Get list of widgets for a specific add-on
Output schemas not documented. Code shows parameter validation but no response structure definitions for any tool. LLMs cannot plan downstream calls or extract required fields without knowing what each tool returns.
update_template lacks parameter documentation. Schema shows 'id' is required but does not describe what fields can be updated or their constraints. Ambiguous parameter design forces LLM guessing.
get_assessment conflates 10+ concerns (WordPress basics, Elementor status, brand styles, theme builder, template stats, pages, add-ons, issues). Should be split into separate discovery tools (get_wordpress_status, get_elementor_status, get_template_stats, etc.) for composability.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 56 | 2026-07-28+ | v2 |
Get Elementor Ally plugin detection status, version, tier, credits remaining, and capabilities
Get comprehensive site assessment including WordPress basics, Elementor status, brand/global styles, theme builder templates, template library stats, pages, add-ons, and detected issues
Retrieve a single template by ID
Get the Elementor data for a template
List all registered Elementeer add-ons with slug, label, version, and capabilities
List all registered add-ons with detailed information including plugin status, widgets, and registration timestamp
List Elementor templates with filtering by type, status, search, category, and pagination
Enable or disable a widget in a specific add-on
Update an existing template (PATCH)
No error handling guidance visible. Code does not show how tools respond to failures (e.g., template not found, permission denied, invalid widget ID). LLMs cannot recover from errors without actionable error messages.
Destructive operations (delete_template) lack confirmation or dry-run support. Agents can permanently delete templates without a safety gate. Should implement confirm_before_execute pattern.