litespeed/get-database-summary reports how many rows each cleanup type would affect: post revisions, orphaned post meta, auto-drafts, trashed posts, spam and trashed comments, trackbacks, and transients.
Read-only. It reports what a cleanup would remove without removing anything.
At a glance
| Ability | litespeed/get-database-summary |
| Toolset | LiteSpeed Cache — toolset/litespeed |
| Group | LiteSpeed Cache › Database Health |
| Requires | LiteSpeed Cache, active on the site |
| Capability | manage_options |
| Safety | Read-only — changes nothing |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Abilities Manager 0.0.34 and later |
How it works
LiteSpeed’s own cleanup cannot be run from an ability — it is bound to its admin screen. Rather than reimplement deletion here, this suite reports the counts and points at the abilities that can do the work.
litespeed/plan-database-cleanup is that pointer: the same counts, with the exact ability to use for each type and a flag saying whether that route is safe.
The counts themselves are useful on their own. A site with two hundred thousand revisions has a database problem worth addressing; a site with four hundred has nothing to gain from a cleanup and should not be running one.
Transients are the type most likely to be large and the least worth worrying about — they expire on their own, and a large transient count usually means a plugin is generating them faster than they expire rather than that anything needs deleting.
Input
This ability takes no input.
What comes back
| Name | Type | What it is |
|---|---|---|
counts | object | How many rows each cleanup type would affect. |
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:
How much cruft is in this database?
It resolves to one call:
{
"ability": "litespeed/get-database-summary",
"parameters": {}
}Worth knowing
- Read-only. Nothing is deleted.
- LiteSpeed’s own cleanup is not runnable from an ability; other abilities do the work.
- A large transient count is usually a symptom, not a problem to delete away.
- Small counts mean a cleanup is not worth running.
Related abilities
- Plan Database Cleanup — the counts plus how to act on them
- Get Autoloaded Options Summary — the other weight
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category