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

wp-mcp-control-server

by mpierre135
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

wp_elementor_insert_widget

Insert a widget into a column or container by providing parent_id from the element list. Set confirm to true when safe mode is active.

Instructions

Insert a widget into a column or container. Requires parent_id from wp_elementor_list_elements. Use confirm:true when safe mode is on.

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>",
      "parent_id": "<parent_id>",
      "widget_type": "<widget_type>"
    },
    "name": "wp_elementor_insert_widget"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoRequired when safe mode is enabled
page_idYes
settingsNo
parent_idYesParent column or container element ID
widget_typeYesWidget type from catalog

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

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

Without annotations, the description carries the full burden. It correctly implies a write operation ('Insert'), but does not disclose potential side effects, reversal capabilities, or success/failure details. The mention of safe mode and confirm adds some transparency, but overall behavioral context is limited.

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?

The description is extremely concise with only two sentences, no redundancy, and no fluff. Every sentence adds value: the first states the core purpose, the second covers usage conditions.

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?

Given the tool has 5 parameters (including a nested object), no output schema, and no annotations, the description is minimal. It covers the essential prerequisite and safe-mode requirement, but lacks information on the settings object, expected response, or error handling, making it moderately complete for an agent.

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?

The schema provides descriptions for 3 of 5 parameters (60% coverage), and the tool description does not add any additional meaning beyond what is in the schema. For example, 'settings' and 'page_id' are not explained further. Baseline 3 is appropriate as 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 description clearly states the action ('Insert a widget'), the target resource ('into a column or container'), and specifies a prerequisite requirement ('Requires parent_id from wp_elementor_list_elements'), effectively distinguishing it from sibling tools like wp_elementor_clone_element or wp_elementor_update_element.

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?

The description provides explicit usage guidance, noting the need for a parent_id obtained from wp_elementor_list_elements and the confirm parameter when safe mode is on. It does not directly state when not to use this tool or list alternatives, but the context is clear enough for an agent.

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