<!-- Generated from Cogny's tool registry. Canonical page: https://cogny.com/integrations/cookiebot/tools -->

# Cookiebot tools in Cogny

Cogny's Cookiebot integration exposes 3 tools (3 read) to an AI agent over MCP. The same tools are available on every plan, from your own AI client or inside the Cogny app.

- **Read** (3): only reads data.
- **Write** (0): creates or changes something.
- **Destructive** (0): deletes, removes or replaces something.

Over MCP your own AI client asks before it runs a write. To take a tool away from your agent, block it in Settings → Integrations.

## Notes

Cookiebot connects with two values from Cookiebot Manager → Settings → Your scripts: the secret API key and the domain group ID (the `cbid` in your banner script). There are no scopes. If the account has more than one domain group, a tool can read another one by passing its ID as `domain_group_id`.

Everything is read-only, because Cookiebot's data API has no write endpoints.

Consent statistics are the numbers in Cookiebot Manager → Consents, per day: opt-ins, opt-outs, implied and active (strict) opt-ins, opt-ins per category (Preferences, Statistics, Marketing), cross-domain consent sharing opt-ins, and consents per country. Rates are computed from them over all recorded consents (opt-ins + opt-outs): `statistics_rate` is the share that allowed the Statistics category, which analytics tools such as GA4 depend on, and `marketing_rate` the share that allowed ad pixels. Cookiebot keeps these statistics for 12 months.

The domain must be written as it is registered in Cookiebot Manager. If Cookiebot doesn't find it, the tool tries once with or without `www.`.

## Known gaps

- Counts are consent submissions, not visitors or sessions. Visitors who never answer the banner aren't counted unless implied consent is switched on, so the numbers can't be divided straight into GA4 sessions.
- No per-consent records (the consent log), no per-page or per-device breakdown, and no hourly data.
- Domains and domain groups can't be listed: the API has no endpoint for them, so pass the domain you want to read.
- Cookie scan results carry Cookiebot's numeric category id; the API doesn't return the category name.
- Banner settings, cookie categories and scans can't be changed or started.
- A wrong API key, a wrong domain group and an unknown domain all get the same "Domain not found" answer from Cookiebot, so the error lists all three causes.

## All tools

| Tool | Kind | What it does |
|---|---|---|
| `get_consent_stats` | Read | See how many visitors accepted or declined cookies on a website, and what share allowed statistics and marketing tracking. |
| `compare_consent_periods` | Read | Compare consent and opt-in rates on a website between two periods, to tell whether a drop in tracked traffic or conversions came from consent. |
| `get_cookie_scan` | Read | List the cookies and trackers Cookiebot's latest scan found on a website, with provider, category, purpose, expiry and whether each waits for consent. |

Exact input schemas come from `tools/list` once Cookiebot is connected; the free plan is enough to check.

Missing something? Your agent can ask for it with `request_feature`.

---

All integrations: https://cogny.com/integrations/tools/index.md
Plans, approvals, limits and data protection: https://cogny.com/buying-guide.md
What Cogny is: https://cogny.com/llms.txt
