Fillout MCP Server

Delete submission

delete_submission

Destructive

Permanently delete a specific submission from a Fillout form. This action cannot be undone, so confirm with the user first.

Instructions

Permanently delete a submission. This cannot be undone, so confirm with the user first.

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>",
      "submissionId": "<submissionId>"
    },
    "name": "delete_submission"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 4, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description adds genuinely new context: the deletion is permanent, irreversible, and requires user confirmation before invocation — exactly the kind of operational caveat the annotations cannot express.

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?

Two short sentences with zero filler; the destructive action is stated first and the confirmation requirement immediately follows. Nothing could be trimmed without losing meaning.

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 two-param destructive tool with full schema coverage and annotations carrying the safety flags, the description covers the essential caveat (irreversibility + confirm first). It omits secondary details such as cascade effects on related data or required permissions, which keeps it just short of complete.

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 100% with only two required params (formId, submissionId), both documented in the schema itself. The description adds no parameter-level detail, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Permanently delete a submission") that clearly distinguishes it from the list/get/create siblings on the same resource and from delete_webhook. It stops short of naming an alternative or scoping behavior, so it is clear but not fully differentiated.

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

Usage Guidelines3/5

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

The description gives one procedural rule ("confirm with the user first") which is real guidance, but says nothing about when deletion is appropriate versus other tools, prerequisites, or whether any soft-delete/restore path exists.

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

Deploy Server