consent/list-cookies returns the cookies the site declares, with the category each belongs to, its domain, how long it lasts and the description shown to visitors.
An empty list is a real answer, and a common one: it means the banner names no cookies at all.
At a glance
| Ability | consent/list-cookies |
| Toolset | CookieYes — toolset/cookieyes |
| Group | CookieYes › Declared Cookies |
| 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
This is the inventory, not the reality. A declared cookie is an entry in a table that the preference centre reads when it builds the list a visitor sees. It does not make the cookie exist, and removing it does not stop the cookie being set.
So the list answers one question precisely: what is this site telling visitors it uses? Comparing that against what the site actually sets is the work, and it is work a person or a scan does — this is one half of the comparison.
Descriptions and durations come back keyed by language, because that is how they are stored. A site offering the banner in three languages has three descriptions per cookie, and any of them can be missing while the others are filled in.
The category filter takes a category ID from consent/list-categories. Without it you get everything.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
category_id | integer | No | Only cookies in this consent category. Omit for all. |
What comes back
| Name | Type | What it is |
|---|---|---|
cookies | array | One entry per cookie: ID, name, category, domain, duration and description, the last two keyed by language. |
count | integer | How many cookies were returned. |
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 cookies does our banner tell visitors about?
It resolves to one call:
{
"ability": "consent/list-cookies",
"parameters": {}
}Worth knowing
- An empty list usually means the inventory was never filled in, not that the site sets no cookies.
- Descriptions are per language. A cookie described in English and blank in German displays blank to German visitors.
- Nothing here inspects the browser. This is what the site declares.
Related abilities
- Declare a Cookie — add a missing entry
- List Consent Categories — the categories these sit under
- Get Cookie Scan Status — when the inventory was last checked
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category