Skip to main content
Glama
t0knight
by t0knight

update_custom_widget

Modify a custom widget's model, name, events, triggers, height mode, and position in an Appsmith app.

Instructions

Update a Custom Widget's model, name, events, triggers, height mode, and/or position.

`default_model` replaces the model the widget reads via `appsmith.model` (dict or JSON
string). `name` renames it. `events` registers the event names the widget can emit
(e.g. `["onRefresh"]`). `triggers` binds those events to expressions, keyed by event
name (e.g. `{"onRefresh": "{{ bootstrap.load() }}"}`) — each is wired into the widget's
dynamicTriggerPathList automatically. `dynamic_height` is `"AUTO_HEIGHT"` or `"FIXED"`.
`left`/`top`/`columns`/`rows` move/resize it. Source code (html/css/js) is not editable
here — use patch_widget_code for targeted in-place source edits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topNo
leftNo
nameNo
rowsNo
eventsNo
columnsNo
triggersNo
widget_idYes
default_modelNo
dynamic_heightNo
Behavior4/5

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

Reveals side effect: triggers are 'wired into the widget's dynamicTriggerPathList automatically.' No annotations, so description carries burden. Could mention immediate application or validation, but already provides useful behavioral context beyond the schema.

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 paragraphs: first sentence states purpose, then parameter explanations. No redundant or extraneous sentences. Information is front-loaded and easy to parse.

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

Completeness5/5

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

Given 10 parameters, 0% schema coverage, no output schema, and no annotations, description covers all necessary information: purpose, parameter semantics, usage constraints, and alternative sibling. Leaves no gaps for an agent to misinterpret.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so description fully compensates. Explains all 10 parameters with specific details: default_model (dict/JSON string), events (array of strings), triggers (keyed by event name), dynamic_height (two enum values), position (left/top/columns/rows). Even notes that triggers are wired automatically.

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?

Clearly states verb 'Update' and resource 'Custom Widget', listing specific aspects (model, name, events, triggers, height mode, position). Distinguishes from sibling patch_widget_code by noting source code is not editable here.

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

Usage Guidelines5/5

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

Explicitly states when not to use: 'Source code (html/css/js) is not editable here — use patch_widget_code for targeted in-place source edits.' Provides clear scenario-based guidance and alternative tool.

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/t0knight/appsmith-mcp'

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