Fillout MCP Server

Create submissions

create_submissions

Create 1-10 form submissions to import data, using question IDs from get_form; API-created entries won't trigger Fillout notifications, workflows, or integrations.

Instructions

Create 1-10 submissions for a form (for example, to import data). Call get_form first to get question ids. Note: submissions created via the API do not trigger Fillout notifications, workflows or integrations.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "formId": "<formId>",
      "submissions": "<submissions>"
    },
    "name": "create_submissions"
  }
}

Input Schema

Name	Required	Description	Default
`formId`	Yes	The form's public ID (from list_forms or the form URL)
`submissions`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 4, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so safety is partly covered. The description adds genuinely useful side-effect context beyond that: API-created submissions do not trigger Fillout notifications, workflows, or integrations. It stops short of stating auth needs, error behavior, or whether partial failures are possible.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with purpose, then prerequisite, then caveat. Nothing is redundant and each sentence carries distinct information.

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?

For a batch-mutation tool with no output schema, the description covers purpose, prerequisite, batch bounds, and the most important side effect. It leaves the return payload (e.g., created submission ids) and per-item failure semantics unaddressed, but the essential call-path information is present.

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 description coverage is 50%; formId is documented in the schema and the description reinforces the question-id linkage by pointing to get_form. However, urlParameters and submissionTime are undocumented in both schema and description, and the accepted value types for questions[].value are left unexplained.

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?

States a specific verb and resource ('Create ... submissions for a form'), adds a concrete scope constraint (1-10) and a motivating use case (data import). It is clearly separable from siblings like create_webhook or delete_submission without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit prerequisite: 'Call get_form first to get question ids,' which routes the agent to the correct sibling before invoking. It offers a use case (import data) but does not state when not to use it or name alternative paths for bulk/large imports.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server