Skip to main content
Glama
elementor-mcp

elementor-mcp

by heaventree

Find and replace across Elementor content

elementor_replace_text
Destructive

Replace a string across Elementor page data, preview affected pages and occurrence counts with a default dry run, then commit confirmed changes safely.

Instructions

Replace a string everywhere it appears in Elementor page data — a phone number, an old brand name, a changed URL. Runs as a dry run by default and reports exactly which pages and how many occurrences it would touch; set dryRun false and confirm true to commit. Every page it edits is snapshotted first. Always read the dry run before committing.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "search": "<search>"
    },
    "name": "elementor_replace_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteNoConfigured site name. Omit to use the default site.
dryRunNoReport without writing. Leave true until you have read the report.
searchYesThe exact string to find.
confirmNoRequired when dryRun is false.
postIdsNoRestrict to these pages.
replaceNoWhat to put in its place. Empty removes it.
postTypesNo
caseSensitiveNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true/openWorldHint=true, and the description adds real context beyond them: the dry-run default, the fact that the dry run reports which pages and how many occurrences, the requirement for confirm when committing, and the guarantee that every edited page is snapshotted first. That covers the risk profile an agent needs before touching a destructive write.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four sentences, front-loaded with the core action, then safety and workflow. Every sentence carries weight. The closing 'Always read the dry run before committing' slightly restates the dryRun schema note, which keeps it from earning a 5.

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 destructive mutation with no output schema, the description supplies the missing safety model (dry run, snapshot, confirm) and describes what the report contains. It stops short of stating hard limits -- how many pages or post types it can span by default, or whether templates and global settings are included -- which an agent would want before committing.

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?

Schema coverage is 75%, so the schema carries most of the meaning. The description still adds the interaction between dryRun and confirm and the consequence of an empty replace, and it signals that the operation is scoped to pages through the dry-run reporting. postTypes and site are not discussed, but overall the description adds real operational meaning.

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 concrete verb and resource -- "Replace a string everywhere it appears in Elementor page data" -- and gives examples (phone number, brand name, URL) that pin down the scope. It does not name a sibling, so an agent must still work out on its own how this differs from elementor_replace_page_tree or elementor_find_elements, which is the only gap.

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?

Describes a clear working procedure: the tool is a dry run by default, the agent should read the report and then set dryRun false with confirm true. That is solid context for the commit path. It gives no explicit exclusion or comparison against alternative replace or find tools, so the when-to-use-this-vs-sibling dimension is left implicit.

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