Delete Submission is a WordPress ability from Fluent Forms — usable via Easy MCP AI, which connects Claude, ChatGPT, and any AI assistant to your site.
Install Free Plugin →Delete Submission
DestructivePermanently delete one entry and its uploaded files.
Needs the Fluent Forms MCP server switched on in FluentForm → Settings → MCP, and WordPress 6.9+ so wp_register_ability() exists (abilities are only registered when the function is present). Reaching the server also requires a logged-in WordPress user holding at least one FluentForm capability. Each ability additionally checks a specific FluentForm capability (e.g. fluentform_dashboard_access, fluentform_forms_manager, fluentform_entries_viewer, fluentform_manage_entries, fluentform_view_payments, fluentform_settings_manager) via the plugin's own Acl system, and every write ability requires a two-step dry_run → confirm_token round-trip through WriteGuard before anything is persisted. Note (from source comments): a WordPress role granted FluentForm access via the Role Manager passes every per-ability capability check, including delete-submission and bulk delete_permanently — the real boundary for such a user is 'has FluentForm access, restricted to their form scope', not per-tool separation; only individually-assigned 'specific forms' managers are gated the way each ability's declared capability implies.
What it does
Permanently and irreversibly deletes a single entry along with any files it uploaded. Because this cannot be undone, the tool's own description steers agents toward update-submission-status with status:trashed when the goal is merely to hide an entry. A lost-response retry is handled by checking the idempotency replay cache before the entry is resolved, since once deleted the id can never resolve again for a normal lookup. Requires dry_run:true first to preview the entry (serial, status, created_at) and obtain a confirm_token, then a repeat call with the same entry_id plus confirm_token to execute.
See it in action
You ask your AI assistant
"Permanently delete entry 245 and its uploaded files."
Inputs
| Name | Type | Required | Description |
|---|---|---|---|
| entry_id | integer | Yes | The submission id to delete. |
| dry_run | boolean | No | Preview the change without writing; returns a confirm_token. |
| confirm_token | string | No | The token from the dry_run preview, required to execute. |
| idempotency_key | string | No | Optional; a retry with the same key will not act twice. |
Returns
On dry_run: the entry_id, form_id, serial, status, created_at, and a permanent:true flag with a confirm_token. On execute: the entry id and deleted:true.
Permission
Requires the fluentform_manage_entries capability.
More Fluent Forms abilities
Add Submission Note
Attach an internal staff note to one entry; not visible to the submitter.
Bulk Update Submissions
Apply one action — read, unread, trashed, favorite, unfavorite, or permanent delete — to up to 200 entries at once.
Create Form
Create a new form from a title and an ordered list of fields, or a basic contact form by default.
Create or Update Email Notification
Create a new email notification or update an existing one — including its recipient.
Get Form
Load one form's full detail, including its field schema, so the agent knows the exact field keys used in submissions.
Get Form Stats
Headline numbers for one form — entry counts by status, total views, and conversion rate.