Skip to main content
Glama
mondaycom

monday MCP Server

Official
by mondaycom

Create Table View

create_view_table

Create a table view on a Monday.com board with filters, sorting, tags, and customizable column visibility, order, and group-by settings.

Instructions

Create a new table-type board view with optional filters, sort, tags, and table-specific settings (column visibility/order and group-by). Use this instead of create_view when you need to configure table-specific settings. For a simple table view, create_view also works.

Filter operators: any_of, not_any_of, is_empty, is_not_empty, greater_than, lower_than, between, contains_text, not_contains_text

Example settings.columns: { "column_properties": [{ "column_id": "status", "visible": true }], "column_order": ["name", "status", "date"] } Example settings.group_by: { "conditions": [{ "columnId": "status" }], "hideEmptyGroups": true }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
boardIdYesThe board ID to create the table view on
nameNoThe name of the view (e.g. "High Priority Items", "My Tasks")
filterNoFilter configuration for the view
sortNoSort configuration for the view
tagsNoTags to apply to the view
settingsNoTable-specific view settings (column visibility/order, group-by)
Behavior4/5

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

Annotations indicate non-readonly and non-destructive. Description adds context about table-specific settings but does not mention permissions, naming conflicts, or side effects beyond creation. Adequate but leaves some unknowns.

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?

Description is concise with two paragraphs and examples. Front-loaded purpose. Could be slightly more structured but overall effective.

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

Completeness4/5

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

No output schema but tool is create operation, likely returns success. Covers main aspects of complex tool with 6 parameters and nested settings. Lacks details on return value or async behavior, but sufficient for typical use.

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 covers all parameters. Description provides examples for settings.columns and settings.group_by, and lists filter operators, adding significant value beyond the schema especially for complex nested objects.

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 creates a 'table-type board view' with optional filters, sort, tags, and table-specific settings. Differentiates from sibling 'create_view' by specifying when to use this tool instead of create_view.

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 recommends using this tool over create_view for table-specific settings and notes create_view works for simple table views, providing clear usage guidance.

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