consent/list-categories returns the consent categories the banner offers — the choices a visitor is actually given — with the cookie count in each and whether it is shown at all.
Names and descriptions are keyed by language.
At a glance
| Ability | consent/list-categories |
| Toolset | CookieYes — toolset/cookieyes |
| Group | CookieYes › Consent Categories |
| Requires | CookieYes, 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
A cookie banner is not a yes-or-no question. It is a set of categories a visitor accepts or rejects individually, and one of them — the strictly necessary one — is not a choice: it loads before anyone decides anything.
Which is why the flags come back alongside the names. A category that is hidden from the preference centre is not one a visitor can reject. A category marked strictly necessary loads regardless. Together those two facts describe how much choice the banner is actually offering, and that is the thing worth auditing.
The cookie count per category is the other half. A category with no cookies in it is a choice about nothing; a necessary category with a tracking cookie in it is a choice taken away.
This is also where cookie writes start, since consent/add-cookie needs a category ID.
Input
This ability takes no input.
What comes back
| Name | Type | What it is |
|---|---|---|
categories | array | One entry per category: ID, name and description keyed by language, whether it is strictly necessary, whether it is visible, its priority and its cookie count. |
count | integer | How many categories 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:
What choices does our cookie banner actually give people?
It resolves to one call:
{
"ability": "consent/list-categories",
"parameters": {}
}Worth knowing
- The strictly necessary category loads before consent. Nothing that tracks belongs in it.
- A hidden category cannot be rejected by a visitor.
- The cookie count is what makes an empty category visible.
Related abilities
- Get Consent Category — one category and its cookies
- Update Consent Category — change how it is presented
- List Declared Cookies — everything the banner names
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category