litespeed/purge-post purges the cached copies of posts by ID.
It is the call after an edit made outside WordPress, which does not trigger LiteSpeed’s automatic purge.
At a glance
| Ability | litespeed/purge-post |
| Toolset | LiteSpeed Cache — toolset/litespeed |
| Group | LiteSpeed Cache › Purging |
| Requires | LiteSpeed Cache, active on the site |
| Capability | manage_options |
| Safety | Writes data |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Abilities Manager 0.0.34 and later |
When the automatic purge does not fire
LiteSpeed hooks WordPress’s save events, so editing a post in the admin purges it and the pages it appears on automatically. That covers almost everything — and then there are the writes that do not go through those hooks.
A direct database update, an import, a migration, a plugin writing post meta with update_post_meta() rather than a save — all of them change what a page renders without firing a save event. The page is stale and nothing knows.
Purging by post ID rather than by URL matters because a post appears on more than its own page: the front page, category archives, tag archives, the feed. LiteSpeed’s own post-purge handles those relationships; purging the post URL alone leaves the archives showing the old excerpt.
IDs that do not exist are reported back rather than silently skipped, so a typo does not look like a successful purge.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
post_ids | array | Yes | The post IDs to purge. |
What comes back
| Name | Type | What it is |
|---|---|---|
purged | array | The post IDs that were purged. |
not_found | array | IDs that do not exist. |
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:
We updated post 412 through the database — clear its cache.
It resolves to one call:
{
"ability": "litespeed/purge-post",
"parameters": {
"post_ids": [412]
}
}Worth knowing
- Purging by ID also clears the archives the post appears on. Purging its URL does not.
- Unknown IDs are reported, not skipped.
- Normal admin edits purge automatically — this is for everything else.
- Idempotent.
Related abilities
- Purge Taxonomy Archives — the archive pages on their own
- Purge URLs — for pages that are not posts
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category