Skip to main content
Glama
elementor-mcp

elementor-mcp

by heaventree

Regenerate Elementor CSS

elementor_flush_css
Idempotent

Clear Elementor's cached CSS so styles regenerate on the next page load. Use it manually when styles look stale after external edits or theme/plugin updates.

Instructions

Clear Elementor's cached CSS so it regenerates on the next page load. The editing tools already do this after every write; call it manually when styles look stale after changes made outside this server, or after a theme or plugin update.

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

Input Schema

NameRequiredDescriptionDefault
siteNoConfigured site name. Omit to use the default site.
postIdNoFlush one page. Omit to regenerate the whole site's CSS.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare non-read-only, idempotent, non-destructive, open-world behavior, and the description adds the useful consequence that the CSS is only rebuilt on the next page load rather than immediately. It does not say whether a whole-site flush is materially slower or heavier than a single-page flush, which is the main remaining behavioral question for this tool.

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, front-loaded with the effect and then the call condition, with no filler or restatement of the title. Every clause carries information an agent needs.

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 two-optional-parameter maintenance tool with no output schema and full annotation coverage, the description supplies purpose, effect timing, and the exact trigger conditions. Nothing needed to decide whether and when to call it is missing.

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 100%, so both parameters are already documented, and the description adds no semantics beyond the schema's own 'Flush one page / omit to regenerate the whole site's CSS' wording. Baseline 3 applies when the schema does the heavy lifting.

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 first sentence states a specific verb and resource ('Clear Elementor's cached CSS') plus the resulting effect ('regenerates on the next page load'). It also implicitly separates itself from the editing tools that flush automatically, so an agent can place it against the sibling write tools without opening a schema.

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

Usage Guidelines5/5

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

Explicit when-not guidance: the editing tools already flush after every write, so this is only for styles made stale by changes outside the server or by a theme/plugin update. That is a genuine condition-based routing rule rather than a generic suggestion.

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