weavely

Create Form

Create a new EMPTY Weavely form. Returns a formId and a live preview URL. PREFER create_form_bulk INSTEAD when the user has described the form they want upfront (e.g. "build me a contact form with name, email, and message"). create_form_bulk creates the form AND all its pages/elements in a single tool call, which is much faster and avoids many sequential permission prompts in MCP clients like ChatGPT. Only use create_form when you genuinely need to start from an empty form and add elements one

Create Form (Bulk)

Create a complete Weavely form (any type) with all pages and elements in a SINGLE tool call. Use this whenever the user describes the form upfront — it is far faster than create_form + many add_* calls, and avoids multiple permission prompts in MCP clients (e.g. ChatGPT). Per element, provide `type` + `label`, plus `options`/`rows` for choice/matrix. Values are auto-generated from labels. Refine details (placeholders, required, theme, logic) with update_element / set_theme / set_settings / set_

Get Form Summary

Get the current form structure: pages, elements (with IDs, types, labels), theme, and settings. Call this to see available page and element IDs before making edits. Requires create_form to have been called first.

Add Element

Add an element to a page. The element is appended to the end of the page. Call this sequentially — NEVER call multiple add_element in parallel. Use get_form_summary to see available pageIds. Element types and their specific params: - Input fields: input-text, input-number, input-email, input-phone-number, input-url, input-time, input-date, text-area - File upload: input-file (supports maxFiles, maxFileSize, allowedFileType) - Choice fields: radio-buttons, checkbox-buttons, dropdown, ranking (re

Update Element

Update an existing element's properties. Only send the fields you want to change. Use get_form_summary to find element IDs. Note: you cannot change an element's type — remove it and add a new one instead.

Remove Element

Remove an element from the form by its ID. Use get_form_summary to find element IDs.

Reorder Elements

Move an element to a new position within the same page or to a different page. Use get_form_summary to see current page and element IDs.

Add Page

Add a new form page. By default it is inserted before the ending page. Use this to create multi-page forms. After adding, use add_element to populate the page.

Remove Page

Remove a form page and all its elements. Cannot remove the ending page or the last remaining form page.

Reorder Pages

Reorder the form pages. Provide the form page IDs in the desired order. The ending page is always kept last automatically — do not include it.

Set Theme

Set the form's visual theme. Choose colors, fonts, layout, and component styles that match the form's topic and tone. Be creative — pick a cohesive palette. Only send what you want to change — unset properties keep their current values. COLORS (all hex values): - primary: main accent color (buttons, highlights) - background: page background - text: general body text - question: question/label text - answer: user input text - secondary: secondary UI elements - surface: input field backgrounds -

Set Settings

Configure form-level settings. Only send what you want to change. Supported language codes: ar, ca, zh-Hans, zh-Hant, hr, cs, da, nl, en, et, fi, fr, de, el, he, hi, hu, id, it, ja, ko, no, pl, pt, ru, es, sv, tr, uk, vi.

Set Logic

Set conditional logic rules and/or event triggers. This replaces ALL existing rules/triggers. Use get_form_summary to see element and page IDs for building conditions. Logic rule structure (FOLLOW THIS EXACTLY): { "id": "<uuid>", "name": "Human-readable rule description", "conditions": [ { "id": "<uuid>", "variable": "field:<elementId>", "operator": "isNotEmpty", "value": null } ], "logicalOperator": "all", "actions": [ { "id": "<uuid>",

Add Outcome

Add an outcome (result) to an existing SCORE or MATCH form. Creates the outcome and its result page in one call. - SCORE: provide `maxScore` (inclusive upper score bound) for all tiers except the highest, which omits it. Outcomes are evaluated in ascending score order — if you add a new top tier, omit its maxScore and make sure the previously-top tier now has one. - MATCH: omit `maxScore`. The respondent is routed to the highest-weighted outcome. After adding outcomes, wire option scores/weigh

Remove Outcome

Remove an outcome (and its result page) from a SCORE or MATCH form by outcome id. Use get_form_summary to find outcome ids.

Set Element Scoring

Set the scoring config on an existing question, based on the form type: - QUIZ: pass `correctAnswer` (the correct option label; an array of labels for checkbox-buttons; literal text for input-text) and optional `points` (default 1). - SCORE: pass `optionScores` — a map of { optionLabel: points }. - MATCH: pass `optionWeights` — a map of { optionLabel: { outcomeName: points } }. This REPLACES the targeted option's existing score/weights, so pass the complete set for each option you include. Use

Publish Form

Publish the form so the user can keep it, share it, and collect real responses. ONLY call this when the user EXPLICITLY asks to publish, save, or share their form. Do NOT call this automatically — the preview URL is sufficient during the building process. Creates a permanent copy of the form and returns an editor URL. The user can create a Weavely account there to claim full ownership. IMPORTANT: If this tool fails, tell the user there was an error publishing and they should try again. Do NOT