Skip to main content
Glama
elementor-mcp

elementor-mcp

by heaventree

List saved templates

elementor_list_templates
Read-onlyIdempotent

List saved Elementor templates—sections, containers, pages, headers, footers, and popups—to find and reuse proven layouts instead of rebuilding them.

Instructions

List the Elementor templates saved on this site — sections, containers, pages, headers, footers and popups. Reusing a proven template is cheaper and more consistent than rebuilding the same layout.

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": "elementor_list_templates"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
siteNoConfigured site name. Omit to use the default site.
typeNoTemplate type: container, section, page, header, footer, popup, single, archive.
searchNo
perPageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, openWorldHint), so the description only needs to add context — and it adds little. It says nothing about whether results are paginated, how many are returned by default, whether items carry full content or only metadata, and there is no output schema to compensate.

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?

Two short sentences with the scope stated first and no wasted clauses. The trailing value proposition is mildly promotional but still earns its place as motivation.

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?

For a zero-required-parameter read-only listing tool with annotations present and no output schema, the main missing element is return shape and pagination behavior. The core scope is otherwise adequately conveyed.

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 coverage is only 40% (page, perPage and search are undocumented), yet the description compensates only for 'type', and even then omits 'single' and 'archive' from the listed kinds. It adds no meaning for the paging or search parameters that an agent would likely need.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('List the Elementor templates saved on this site') and enumerates the template kinds it covers, which implicitly separates it from elementor_list_pages and elementor_get_template. It stops short of naming any sibling explicitly, so the differentiation is inferential rather than stated.

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?

The second sentence ('Reusing a proven template is cheaper and more consistent than rebuilding') hints at why to call it, but gives no explicit when-to-use/when-not conditions and no routing to elementor_apply_template, elementor_get_template, or elementor_import_template. Usage is implied rather than specified.

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