litespeed/get-media-settings reads every lazy-loading and media setting: image and iframe lazy load, the placeholder, the exclusion lists, and the viewport-image toggles.
It is the configuration read; litespeed/get-media-status reports what is actually happening.
At a glance
| Ability | litespeed/get-media-settings |
| Toolset | LiteSpeed Cache — toolset/litespeed |
| Group | LiteSpeed Cache › Images & Lazy Load |
| 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
Every settings read in this suite returns the same shape — key, current value, type, and whether the key is writable — and every settings write takes the same shape back: a map of key to value, applied as a patch. Keys are owned by exactly one area, and litespeed/list-settings-areas is the map of which area owns what.
Lazy loading is the setting most likely to be blamed for a problem it did not cause and most likely to be causing a problem nobody blamed it for. Images that never appear, images that appear late, a page that renders blank for a moment — all of those are lazy-loading symptoms, and all of them have other causes too.
Reading the whole area is what separates them. The exclusion lists in particular are where the history lives: an image class excluded two years ago still shapes what the site does today.
The viewport-image toggles are readable here and worth understanding before you change them, because they depend on data this suite cannot generate.
Input
This ability takes no input.
What comes back
| Name | Type | What it is |
|---|---|---|
settings | array | One row per setting: its key, its current value, its type, and whether this suite can write it. |
count | integer | How many settings the area holds. |
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 is lazy loading configured here?
It resolves to one call:
{
"ability": "litespeed/get-media-settings",
"parameters": {}
}Worth knowing
- Configuration only.
litespeed/get-media-statusreports the behaviour. - The exclusion lists carry the site’s history with lazy loading.
- Viewport toggles depend on data generated outside this suite.
Related abilities
- Get Media Status — what is actually happening
- Update Lazy Load Settings — change it
- Update Media Exclusions — hold images back
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category