Skip to main content
Glama

add_widget

Append a widget to a section, column, or container in an Elementor page. Specify parent container and widget type to add elements like heading, text, button, or image. Confirms addition with a second read.

Instructions

Append a new widget to a parent container (section, column, or container) on a page. Re-reads to confirm the new widget exists under the parent. Two-call confirmation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
site_idNo
page_idYes
parent_idYesId of the section/column/container that will receive the widget.
widget_typeYese.g., 'heading', 'text-editor', 'button', 'image'.
settingsNo
confirmationNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeYes
page_idYes
confirmation_tokenNo
backup_meta_keyNo
css_flushNo
mutatedNo
warningsNo
verificationNo
parent_idYes
widget_typeYes
new_widget_idNo
Behavior4/5

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

Discloses two-call confirmation and re-reading behavior beyond annotations. Does not mention all side effects but adds context with openWorldHint.

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?

Single sentence with behavioral note; concise and front-loaded. Could be slightly more structured.

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?

Output schema exists, so return values are covered. But description omits how to use settings and confirmation; for a creation tool with nested objects, more context would help.

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 description coverage is low (33%), and description adds no parameter-level details beyond schema. Key parameters like confirmation and settings are unexplained.

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?

Describes specific verb 'Append' and resource 'widget to parent container'. Includes behavioral detail (re-reads, two-call confirmation). Clearly distinguishes from siblings like delete_widget, move_widget.

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 via parent container types, but no explicit guidance on when to use vs. alternatives or when not to use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Mogacode-ma/elementor-mcp-agent'

If you have feedback or need assistance with the MCP directory API, please join our Discord server