Skip to main content
Most MCP clients load every tool schema into the model’s context at the start of every conversation. With AdLoop’s full catalog that is a noticeable share of the context window, paid before you type a word. Toolsets let you expose a subset.

​
The toolsets

​
Narrowing Google Ads

You can also pick part of Google Ads instead of the whole ads toolset (on AdLoop Cloud: tick Google Ads when creating a key and choose its scope): ads:read,ga4 suits audits and diagnosis; ads:plan alone suits keyword research. health_check and confirm_and_apply are always included, whatever you select, so diagnostics and the safety gate can never be filtered away.

​
What it saves

Measured against the live tools/list: ads:read,ga4 costs about 40% of ads,ga4, and ads:plan alone about 5% of the full catalog. Toolsets are per consumer, not per install: one AdLoop setup can serve a trimmed Cursor and a full-catalog Claude Code side by side.

​
AdLoop Cloud: per API key

Pick toolsets when creating a key under Settings → API keys. The server then trims that key’s advertised tool list and refuses calls outside the selection, with a clear message pointing back to the dashboard. Existing keys are unrestricted until you say otherwise.

​
Self-hosted: environment variable

Set it in your MCP client’s configuration (the adloop init wizard offers this and writes it into the snippets). Unset means the full catalog; unknown names fail at startup listing the valid ones.