elementor/empty-trash permanently deletes every trashed Elementor template. It refuses without confirm: true.
There is a real reason to do this beyond tidiness.
Before you run it
Every trashed template goes at once, and each one is a design that exists nowhere else. Template trashes accumulate over years and typically contain a mix of genuine rubbish and one thing somebody will want back. List the trash first with elementor/list-templates and status=trash, and export anything worth keeping.
At a glance
| Ability | elementor/empty-trash |
| Toolset | Elementor — toolset/elementor |
| Group | Elementor › Templates & Theme Builder |
| Requires | Elementor, active on the site |
| Capability | manage_options |
| Safety | Destructive — deletes stored values, and refuses to run without confirm: true |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Abilities Manager 0.0.34 and later |
How it works
A trashed Theme Builder template keeps its display conditions, and Elementor’s conflict checking still takes them into account. A new header that cannot claim the condition it wants is sometimes losing to a template that was trashed two years ago.
That is a genuinely confusing state — the conflicting template does not appear in any normal listing — and emptying the trash resolves it.
The cost is that template designs are not recoverable afterwards. A trash accumulated over years contains work nobody remembers, and some of it is worth keeping.
So the sequence is: list the trash, export anything of interest, then empty.
Idempotent: emptying an empty trash is a no-op.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
confirm | boolean | Yes — must be true | The irreversibility gate. Without it the call is refused before anything is touched. |
What comes back
| Name | Type | What it is |
|---|---|---|
deleted | integer | How many templates were removed. |
success | boolean | Whether the call completed. |
message | string | A one-line summary of what happened, suitable for showing a human. |
error_code | string | Present only on failure — a stable machine-readable reason, such as a missing field, a wrong field type or an unmet confirmation. |
Example
Ask your assistant:
Empty the Elementor template trash.
It resolves to one call:
{
"ability": "elementor/empty-trash",
"parameters": {
"confirm": true
}
}Worth knowing
- Trashed Theme Builder templates still affect condition conflicts.
- List and export before emptying.
- Designs are unrecoverable afterwards.
- Idempotent.
Related abilities
- List Elementor Templates — see what is in the trash
- Export Elementor Template — keep what matters
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category