Weavely Forms & Surveys

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 (require options; support randomize; radio/checkbox-buttons also support allowOtherOption) - Image choice: image-choice (requires options; supports multiple selection. NOTE: to assign images to options, use the Weavely platform after publishing) - Single checkbox: checkbox (a single yes/no toggle; supports defaultChecked) - Matrix: matrix (a grid question. matrixRows are the row labels, matrixColumns are the column options [{label, value}], matrixMultiple allows selecting multiple columns per row) - Rating: star-rating (defaults to 5 stars; supports stars count), scale-rating (defaults to 10; supports scales count), range-slider (defaults 0-100; supports min, max, step) - Display: heading, paragraph (label is the display text; paragraph supports HTML) - Media: embed-html (codeSnippet), embed-audio (url), embed-video (url). NOTE: the image element is not available through this tool — use the Weavely platform to add images. - Special: signature For choice types, provide options as [{label: "...", value: "..."}]. The value is the internal identifier (use lowercase-kebab-case).

add_element

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/weights toward them with set_element_scoring.

add_outcome

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.

add_page

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 at a time. IMPORTANT: This MUST be the first tool you call — all other tools require the formId returned by this tool. IMPORTANT: Call all tools ONE AT A TIME, sequentially. NEVER call multiple tools in parallel. IMPORTANT: Pass the formId from this response to ALL subsequent tool calls. IMPORTANT: Always share the previewUrl with the user in your response text so they can open the form preview. The form is a PREVIEW only — it is not published yet. The user CANNOT claim, sign up, or take ownership of the form from the preview URL. The ONLY way to publish is through the publish_form tool. When the user wants to publish, save, or share their form, you MUST use the publish_form tool. Do NOT tell them to visit the preview URL to claim or publish — that is not possible. After calling this, use add_element, add_page, set_theme, etc. to build the form step by step. Every subsequent tool call refreshes the live preview widget automatically — no extra "show preview" call is needed. PLATFORM FEATURES NOT AVAILABLE IN THIS TOOL: Weavely supports many features that are only available on the Weavely platform (not through this tool). If the user asks about any of the following, let them know the feature exists but they need to publish their form first and then configure it on the Weavely platform: - Integrations: Make, Zapier, n8n, Google Sheets, HubSpot, Airtable, Notion, and more - Email notifications: receive an email on each submission, or send confirmation emails to respondents - Social media preview: customize the Open Graph image, title, and description for link sharing - Custom domain: serve the form on the user's own domain - Form icon: customize the favicon/icon shown in the browser tab - Embed codes: get HTML embed snippets to embed the form on any website - Image content: adding images to image-choice options or using the image element requires the Weavely platform (image uploads are not supported through this tool) Tell the user to publish first (via publish_form), then visit the Weavely editor to set these up.

create_form

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_logic AFTER this returns. Element types: input-text, input-number, input-email, input-phone-number, input-url, input-time, input-date, text-area, input-file, radio-buttons, checkbox-buttons, dropdown, ranking, image-choice, checkbox, matrix, star-rating, scale-rating, range-slider, heading, paragraph, embed-html, embed-audio, embed-video, signature. FORM TYPES (set via `type`, default "universal"): • universal — standard data collection (contact forms, surveys). An ending page is added automatically; customize it with `ending`. • quiz — objective right/wrong quiz with a total score. Set type:"quiz". On each scorable question (radio-buttons, checkbox-buttons, dropdown, input-text) set `correctAnswer` (the correct option label; an array of labels for checkbox-buttons) and optional `points` (default 1). Determine the correct answers yourself — do NOT ask the user. The ending page shows the score; use `ending` with piping like "You scored {{quiz:quiz-score}} out of {{quiz:max-score}}". Optional `instantFeedback` shows right/wrong after each question. • score — lead-gen / assessment that scores the user and routes them to an outcome tier (NO objective correct answer). Set type:"score" and define `outcomes` as tiers in ascending order, each with a `maxScore` (inclusive upper bound) EXCEPT the last/highest tier which omits maxScore. On each choice option set a `score`. Write outcome page content (`heading`/`body`) directly to the respondent, but NEVER reveal the tier name to them (don't write "You are a Hot Lead"). • match — personality / recommendation quiz. Set type:"match" and define `outcomes` (the possible results). On each choice option set `weights` mapping outcome NAME → points (one option may feed several outcomes). The highest-scoring outcome's page is shown. Default weight 1; figure out the mappings yourself. For score/match, outcome pages ARE the ending pages — do not add a separate ending. The respondent is routed to the matching outcome page automatically. IMPORTANT: Always share the previewUrl with the user in your response text. The widget renders automatically where supported; the URL is the fallback.

create_form_bulk

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.

get_form_summary

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 suggest visiting the preview URL to claim or publish — that is NOT possible. The preview URL is a temporary link that cannot be claimed or converted into a permanent form.

publish_form

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

remove_element

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

remove_outcome

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

remove_page