Skip to main content
Glama
mondaycom

monday MCP Server

Official

Create WorkForm Submission

create_form_submission

Submit a complete response to a monday.com WorkForm. Gather all answers upfront, then send them with the form token to receive a submission ID.

Instructions

Submit a response to a monday.com WorkForm. Use get_form first to retrieve the WorkForm, then:

  • Inspect each question's showIfRules to determine which questions are conditionally shown based on previous answers.

  • Inspect each question's settings for any answer constraints (e.g. rating limits, select options, label limits).

  • Take note of any titles, descriptions, and content blocks to present the form naturally as you walk the user through it.

  • Take note of pages and question order to present questions in the correct sequence. Gather all answers upfront before calling this tool — do not submit one question at a time. Accepts a bare form token, a full WorkForm URL (e.g. https://forms.monday.com/forms/{form_token}?r=use1), or a shortened wkf.ms URL (e.g. https://wkf.ms/4tqP28t) — shortened URLs are automatically resolved by following the redirect. Returns the submission ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
form_tokenYesThe unique token identifying the WorkForm. Can be a bare token, a full WorkForm URL (e.g. https://forms.monday.com/forms/abc123?r=use1), or a shortened wkf.ms URL (e.g. https://wkf.ms/4tqP28t). Shortened URLs are automatically resolved by following the redirect.
answersYesArray of answers to submit. Each answer specifies a question_id and the value for that question type.
form_timezone_offsetYesThe timezone offset of the submitter in minutes (e.g. -120 for UTC-2, 0 for UTC).
passwordNoThe password for the WorkForm. Only required if the WorkForm has password protection enabled (check features.password.enabled from get_form). If required, ask the user for the password before submitting.
tagsNoTags to attach to the submission — each tag maps a value to a specific board column.
Behavior4/5

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

Annotations indicate write operation (readOnlyHint false). The description adds value by detailing token resolution, the need to gather answers upfront, unsupported subitems, and the return of a submission ID. It does not contradict annotations.

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?

The description is structured with a clear opening sentence followed by a bulleted list of steps. While detailed, every sentence adds value without redundancy. Slightly verbose but justified by complexity.

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?

Given 5 parameters, 3 required, and no output schema, the description covers the workflow thoroughly, referencing get_form, explaining token handling, and noting unsupported subitems. It adequately prepares the agent for correct usage.

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

Parameters4/5

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

Schema coverage is 100%, but the description adds context beyond the schema, such as explaining the form_token URL formats, auto-resolution, and the requirement to gather all answers. It also clarifies the answers array structure and unsupported subitems.

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 'Submit a response to a monday.com WorkForm.' It uses a specific verb (submit) and resource (WorkForm), and distinguishes itself from sibling tools like get_form and form_questions_editor by providing a detailed 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?

The description explicitly instructs to 'Use get_form first' and 'Gather all answers upfront — do not submit one question at a time.' It also explains acceptable token formats and auto-resolution of shortened URLs, providing clear context for when and how to use the 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/mondaycom/mcp'

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