elementor-mcp-agent

list_elementor_templates

Read-onlyIdempotent

Retrieves Elementor templates (sections, pages, popups, headers, footers, single/archive templates, global widgets) from a WordPress site, with optional type filter to narrow results.

Instructions

List Elementor library entries on a site: saved sections, pages, popups, headers/footers (Theme Builder Pro), single/archive templates (Theme Builder Pro), and global widgets. Type filter narrows results.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_elementor_templates"
  }
}

Input Schema

Name	Required	Default
`site_id`	No
`type`	No	any
`per_page`	No

Output Schema

Name	Required	Description	Default
`total`	Yes
`templates`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0May 27, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint. Description adds behavioral context about what templates are included (e.g., Theme Builder Pro items) and the type filter, which is useful beyond annotations.

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?

Two concise sentences that front-load the purpose and list contents. No wasted words.

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?

With an output schema existing, return format need not be described. However, it does not clarify that site_id is required (schema has no required array) or address pagination/errors. Adequate but has gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so description must compensate. It only mentions the type filter, ignoring site_id and per_page. Minimal added meaning beyond 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?

Description clearly states action ('List') and specific resource ('Elementor library entries') with enumeration of included types (sections, pages, popups, etc.), distinguishing it from siblings like 'list_elementor_pages' and 'list_global_widgets'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit when-to-use vs alternatives, but the description implies usage for listing library entries and the type filter. Could benefit from contrast with similar list tools.

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