Skip to main content
Glama
elementor-mcp

elementor-mcp

by heaventree

Read or write site custom CSS

elementor_custom_css
Destructive

Read or replace site-wide custom CSS stored in the Elementor kit; omit CSS to inspect current styles. Elementor renders this CSS only on Pro.

Instructions

Read the site-wide custom CSS held on the Elementor kit, or replace it. Passing css writes it; omitting css just reads. Note that Elementor only renders this on Pro.

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

Input Schema

NameRequiredDescriptionDefault
cssNoNew CSS. Omit to read the current value.
siteNoConfigured site name. Omit to use the default site.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the annotations, the description discloses that a write fully replaces the existing CSS ("replace it" — destructive overwrite, not merge) and that Elementor only renders this CSS on Pro, a silent-no-op gotcha the agent could not learn from readOnlyHint=false/destructiveHint=true. It does not mention permissions, backup/snapshot options, or what happens to CSS on non-Pro sites that are written to.

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?

Three short sentences with zero waste: the capability comes first, the parameter-driven mode switch second, the Pro rendering caveat last. Nothing is repeated from the schema or the title.

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 two-optional-parameter, no-output-schema tool with annotations covering the safety profile, the description supplies the essential mode semantics and the biggest environmental caveat (Pro-only rendering). Minor gaps remain around empty-string behavior and whether the read returns raw CSS, but nothing an agent needs to select and invoke 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% and the schema already documents both parameters, including "Omit to read the current value" for css. The description adds useful framing (css is site-wide and stored on the kit) but no syntax, format, or validation detail beyond the schema, so the baseline 3 applies.

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?

"Read the site-wide custom CSS held on the Elementor kit, or replace it" names a specific verb (read/replace), a specific resource (custom CSS), and its scope (site-wide, on the Elementor kit). The dual read/write nature is stated up front in one clause, so an agent knows exactly what surface this tool touches versus page/element sibling tools.

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?

"Passing css writes it; omitting css just reads" gives explicit mode-selection guidance tied to a concrete parameter condition, which is the main usage decision for this tool. It stops short of naming alternatives (e.g. a CSS-flush sibling) or stating when a write should not be attempted, so it is clear context rather than full when/when-not routing.

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