Camberstack: Google Ads

View saved version →

---
name: get-started
description: How to use Camberstack to read a Google Ads account, Search Console and Google Analytics 4, and make only the changes the user approves. Use at the start of any Google Ads, Search Console or GA4 task.
---

# Using Camberstack

Camberstack connects the user's Google Ads account (and, optionally, Search Console and Google Analytics 4).

1. **Start with `list_accounts`.** Answer questions with `account_overview` and `run_gaql` (read-only GAQL `SELECT`).
2. **To change something:** call the `propose_` tool for that change (`propose_pause_campaign`,
   `propose_set_daily_budget`, `propose_mark_key_event`, …), show the user the summary, including any ⚠ line, and ask
   for approval. Only then call `apply_changes`.
3. **Never call `apply_changes` unless the user has explicitly approved that specific proposal in this conversation.**
   Every applied proposal can be reversed with `propose_undo`, which makes a reversing proposal to approve and apply;
   `change_history` lists what was applied.
4. **Each Google service is added separately.** When a result says Search Console or Analytics isn't part of the
   connection, give the user its `grant_url` (one click adds it). Never tell them to reconnect.
5. For `keyword_ideas` and `keyword_metrics`, pass the account's own market: `location_ids` default to the United States.
6. **Search Console is read-only.** Lead with `search_console_summary` (per-query rows leave out rare queries).
   Camberstack can't request indexing or submit sitemaps; the user does that in Search Console.
7. **Account 000-000-0001 is a demo** with sample data: anyone can try every tool on it, and changes there never
   touch Google. Always say when you are using it.