Skip to main content
Glama
Sign In
wp-mcp-control-server

wp-mcp-control-server

by mpierre135
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

wp_elementor_update_text

Update Elementor heading or text widgets by matching existing text and replacing it with new content, with a snapshot created before changes for rollback.

Instructions

Find a heading or text-editor widget by matching existing text and replace it. Creates a snapshot before updating.

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": {
      "page_id": "<page_id>",
      "match_text": "<match_text>",
      "new_text": "<new_text>"
    },
    "name": "wp_elementor_update_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
page_idYes
new_textYesReplacement text
match_textYesExisting text to find (partial match supported)
widget_typeNoWidget type: heading, text-editor, or raven-headingheading

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations provided. Description discloses snapshot creation before update, which is a behavioral trait. However, it does not discuss permissions, error handling, or destructive potential beyond basic replacement.

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 that front-load the action. No unnecessary words; every sentence provides essential information.

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

Completeness3/5

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

Description covers core action and snapshot creation but omits return value, error behavior (e.g., widget not found), and required permissions. For a mutation with no output schema, more detail on outcomes would be beneficial.

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 coverage is 50% (only widget_type and match_text have descriptions). Description mentions 'match existing text' but doesn't add meaning for page_id or new_text beyond what schema provides. No parameter format or constraints are clarified.

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?

Description clearly states it finds and replaces text in heading or text-editor widgets. This specific verb-resource combination distinguishes it from siblings like wp_elementor_insert_widget or wp_elementor_update_button.

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

Usage Guidelines3/5

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

Implies usage for updating widget text, but no explicit when-to-use or when-not-to-use guidance is provided. No mention of prerequisites or comparison to sibling tools (e.g., wp_elementor_update_element).

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

Deploy Server

Other Tools