Skip to main content
Glama
mondaycom

monday MCP Server

Official
by mondaycom

Create Widget

create_widget

Create data visualization widgets in monday.com dashboards or board views by configuring settings based on widget type schema.

Instructions

Create a new widget in a dashboard or board view with specific configuration settings.

This tool creates data visualization widgets that display information from monday.com boards:
**Parent Containers:**
- **DASHBOARD**: Place widget in a dashboard (most common use case)
- **BOARD_VIEW**: Place widget in a specific board view

**Critical Requirements:**
1. **Schema Compliance**: Widget settings MUST conform to the JSON schema for the specific widget type
2. **Use all_widgets_schema first**: Always fetch widget schemas before creating widgets
3. **Validate settings**: Ensure all required fields are provided and data types match

**Workflow:**
1. Use 'all_widgets_schema' to get schema definitions
2. Prepare widget settings according to the schema
3. Use this tool to create the widget

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
parent_container_idYesID of the parent container (dashboard ID or board view ID)
parent_container_typeYesType of parent container: DASHBOARD or BOARD_VIEW
widget_kindYesType of widget to create: i.e CHART, NUMBER, BATTERY
widget_nameYesWidget display name (1-255 UTF-8 chars)
settingsNoWidget-specific settings as JSON object conforming to widget schema. Use all_widgets_schema tool to get the required schema for each widget type.
Behavior4/5

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

Annotations are minimal (readOnlyHint false, destructiveHint false); description adds validation requirements and parent container context but does not discuss error handling or concurrency.

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?

Well-structured with headings and bullet points, front-loaded purpose. Slightly longer than minimal but each section earns its place.

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?

Covers workflow, prerequisites, parent container types, and settings validation. No output schema exists, but description sufficiently explains creation behavior.

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?

Schema coverage is 100%, so baseline 3. The description reinforces the need for schema validation for 'settings' but does not add new semantic detail beyond schema descriptions.

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?

Clear verb 'Create' and resource 'widget', specifies placement in dashboard or board view, differentiates from sibling tools like all_widgets_schema by describing workflow.

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 prerequisite use of all_widgets_schema, gives step-by-step workflow, and outlines critical requirements for schema compliance and validation.

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/mondaycom/mcp'

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