Skip to main content
Glama
elementor-mcp

elementor-mcp

by heaventree

List configured sites

elementor_list_sites
Read-onlyIdempotent

Lists available WordPress sites and identifies the default one. Call it first when unsure which site name to pass to other Elementor tools.

Instructions

List the WordPress sites this server can reach, with which one is the default. Call this first when you are unsure which site name to pass to other tools.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety and repeatability are covered. The description adds one genuinely useful behavioral fact — that the response identifies the default site — but says nothing about how 'reachable' is determined (configured credentials, network probe) or what happens when no sites are configured. Adequate, not rich.

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 short sentences with zero waste: the capability and the default-site detail come first, followed by the routing advice. Nothing is buried or repeated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-argument, read-only listing tool with full annotation coverage and no output schema, the description supplies everything an agent needs: what is returned (reachable sites plus the default) and when to invoke it. Further detail would be padding.

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?

The tool takes zero parameters, so the baseline is 4 and the description has no parameter semantics to compensate for. It correctly avoids restating a nonexistent input 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?

States a specific verb (list) and resource (the WordPress sites this server can reach), plus a distinguishing detail: it also reports which site is the default. The resource is unambiguous against siblings like elementor_list_pages or elementor_list_templates, so an agent can select it without opening the schema.

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?

Gives an explicit trigger: 'Call this first when you are unsure which site name to pass to other tools.' That both names the downstream consumers and implies the when-not case (skip it if the site name is already known). It stops short of stating exclusions outright, but the routing intent is clear.

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