elementor-mcp-agent

wp_elementor_flush_css

Idempotent

Flush Elementor's CSS cache after programmatic _elementor_data updates. Supports site-wide or per-page clearing with automatic REST, wp-cli, or direct fallback.

Instructions

Flush Elementor's CSS cache on a site using the 3-level fallback strategy (REST endpoint → wp-cli native → option/meta delete). Always call after writing _elementor_data programmatically.

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

Input Schema

Name	Required	Description	Default
`site_id`	No
`page_id`	No	Optional: flush only this page's cache. If omitted, flushes site-wide.

Output Schema

Name	Required	Description	Default
`method`	Yes
`details`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0May 27, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations declare idempotentHint=true and destructiveHint=false, and the description adds the fallback strategy and correct usage context. No contradictions; disclosure is adequate.

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, front-loaded with verb and resource, no redundant information. Every sentence 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?

With annotations and an output schema present, the description covers purpose, strategy, and usage advice. Lacks details on failure modes or edge cases but sufficient for the tool's simplicity.

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 covers 50% of parameters (page_id has description, site_id lacks). Description does not add meaning for site_id, relying on context. Semantics partially addressed.

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?

The description clearly states the tool flushes Elementor's CSS cache and specifies the 3-level fallback strategy, distinguishing it from siblings that manipulate content or perform other operations.

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?

Explicitly states to call after writing _elementor_data programmatically, providing clear context. Lacks explicit exclusions or alternatives but the instruction is actionable.

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