Report which marketing data sources are configured (no secrets revealed). Call first if a tool says 'not configured'.

List Search Console properties the service account can access (confirm the SA is granted + the exact siteUrl).

Search Console Search Analytics — clicks / impressions / CTR / position grouped by dimension(s). The core SEO tool (same data as the GSC Performance export, but live + filterable).

List submitted sitemaps + processing status for a property.

URL Inspection — index/coverage status, last crawl, canonical, mobile usability for one URL.

GA4 Data API runReport — sessions, users, conversions, events, channels. Flexible dimensions + metrics over a date range.

GA4 realtime report (active users in the last 30 min).

[GBP] List Business Profile accounts. NOTE: the Business Profile APIs require Google to approve API access (allowlist) first.

[GBP] List locations for an account (name, title, address, website, categories).

[GBP] Daily performance time series for a location: impressions (maps/search × desktop/mobile), call clicks, website clicks, direction requests, conversations, bookings.

[GBP] List reviews for a location (rating, comment, reviewer, time, any reply).

[GBP][WRITE] Post (or update) the business reply to a review.

Meta Graph / Marketing API call — flexible escape hatch, READ and WRITE. method defaults GET; POST to create/update (e.g. path='', params={status:'PAUSED'}), DELETE to remove. Does anything the token's scopes allow.

[Meta] Facebook Page insights (impressions, engagement, fans, etc.).

[Meta] Ad account insights (impressions, clicks, spend, actions, CPC, CTR). Only returns data if you actually run Meta ads.

[Meta] List ad accounts the token can access (id, name, status, spend, currency, business). NOTE: amount_spent is in the currency's MINOR unit (cents/pence) — divide by 100 for the real figure. (A SYSTEM-USER token returns [] here — use meta_graph on '/owned_ad_accounts' instead.) Start of an ads audit.

[Meta] List Business Manager businesses the token can access.

[Meta] List Facebook Pages the token manages (id, name, category, fans).

[Meta] List campaigns on an ad account (id, name, status, effective_status, objective, budget, dates). NOTE: daily_budget/lifetime_budget are in the currency's MINOR unit (cents/pence — ÷100). The core tool for finding dead/clutter campaigns.

[Meta][WRITE] Change a campaign's status — ACTIVE / PAUSED / ARCHIVED / DELETED. The tidy verb for dead campaigns (prefer ARCHIVED over DELETED — reversible).

[Meta] List custom audiences on an ad account (id, name, size, subtype, status, dates).

[Meta][WRITE] Delete a custom audience (destructive — removed, not archived).

[Meta] List ad pixels / datasets on an ad account (id, name, last_fired_time) — spot stale/duplicate pixels.

GA4 Admin: list the accounts + properties you can access, including each property's NUMERIC id — use this to discover GA4_PROPERTY_ID.

GA4 Admin: list key events (conversions) on a property.

GA4 Admin [WRITE]: mark an event name as a Key event (conversion). e.g. eventName='generate_lead'.

GA4 Admin: list custom dimensions on a property.

GA4 Admin [WRITE]: register an event parameter as a custom dimension (e.g. surface a 'step' param as 'Booking Step').

GA4 Admin: list data streams (web/app) on a property — incl. the measurement id.

GA4 Admin API escape hatch — any method/path under analyticsadmin v1beta (audiences, property/stream updates, etc.). WRITES are real; PATCH usually needs a updateMask query.

GSC [WRITE]: submit / resubmit a sitemap.

GSC [WRITE]: remove a sitemap (re-submittable).

GSC [WRITE]: add a property to Search Console (ownership still has to be verified separately).

Indexing API [WRITE]: ask Google to (re)crawl a URL. NOTE: officially for JobPosting/BroadcastEvent pages; pinging general URLs works but is unofficial.

Google Tag Manager API v2 escape hatch — any method/path under tagmanager/v2. Discover: GET 'accounts', then '/containers', then '/workspaces'. Manage: GET/POST '/tags' | '/triggers' | '/variables'; create a version (POST ':create_version'); publish (POST ':publish'). WRITES + PUBLISH are real and affect the live site — build in a workspace, publish deliberately.