Skip to main content
Glama
elementor-mcp

elementor-mcp

by heaventree

List pages and posts

elementor_list_pages
Read-onlyIdempotent

Lists WordPress pages, posts, and templates by newest edit, showing whether each uses Elementor; filter with elementorOnly to skip content not built by the page builder.

Instructions

List WordPress pages, posts and templates, newest edited first, with whether each is built with Elementor. Use elementorOnly to skip content the page builder does not own.

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_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
siteNoConfigured site name. Omit to use the default site.
typeNoPost types to include. Defaults to page and post.
searchNoMatch against title and content.
statusNoPost statuses to include.
perPageNo
templateTypeNoFilter by Elementor template type, e.g. wp-page, header, footer, popup.
elementorOnlyNoOnly return posts actually built with Elementor.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and openWorld, so the safety profile is covered. The description adds real behavioral context beyond them: results are returned 'newest edited first' and each entry carries whether it is built with Elementor, which tells the agent what the read returns and how it is ordered.

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 sentences, zero filler, with the scope, ordering, and result field front-loaded before the single parameter tip. Every clause earns its place.

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 an 8-parameter read with no output schema, the description covers what matters most: the entity set, the sort order, the per-item Elementor flag, and the filtering shortcut. Pagination and the search/status filters are left entirely to the schema, which is acceptable but not complete.

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

Parameters3/5

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

Schema coverage is 75%, so the schema already documents most parameters and the baseline is 3. The description extends elementorOnly with the intent 'skip content the page builder does not own', which is a useful gloss, but it says nothing about page, perPage, search, status, or templateType, so it does not materially raise the bar.

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 and resource set ('List WordPress pages, posts and templates') plus the ordering and the Elementor flag per item, so an agent knows the shape of the result. It does not distinguish itself from elementor_list_templates, which overlaps on the 'templates' part of the scope, so it falls short of a 5.

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 only routing guidance is 'Use elementorOnly to skip content the page builder does not own', which is a parameter tip rather than a when-to-use-this-vs-alternatives statement. Nothing says when to prefer elementor_get_page, elementor_get_page_tree, or elementor_list_templates instead, so usage is implied rather than stated.

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