Google Ads / API Reference
gads_search_geo_targets
Google Ads tool (extended/low-level coverage). For common tasks prefer the RECOMMENDED google_ads_* actions; use these only for advanced operations those don't cover. Search geo target locations by name to get the IDs campaign targeting takes. Geo targets are global constants, not account data, so this needs no account. That matters: the previous version demanded a customer_id and refused the call without one, which is the error this tool was reported failing with. customer_id is still accepted, and ignored, so callers that pass it to everything keep working. Args: query: Location name to look up, e.g. "Tel Aviv", "Greater London". locale: Language for the returned names. Defaults to "en". country_code: Optional two-letter country code to restrict results, e.g. "IL".
This is a read-only tool: it searches geo targets from your Google Ads account. It changes nothing.
Ask Claude
You do not call this tool yourself. Ask for the outcome and the client picks the tool:
Search geo targets in my Google Ads account for [query].
It takes 1 required and 3 optional parameters.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
query | string | Yes | Query |
locale | string | No | Locale |
country_code | string | No | Country Code |
customer_id | string | No | Customer Id |
Related Google Ads tools
Before you can call it
This tool needs a connected Google Ads account. The Google Ads connect guide covers the OAuth flow and the permissions it asks for, and the quickstart gets a client talking to the server in about five minutes.
Workflows that use this
Rather than calling tools one at a time, these skills run a whole procedure against the same account:
- Google Ads — Audits & Health
- Google Ads — Keywords
- Google Ads — Negative Keywords
- Google Ads — Bids & Budgets
Start free — 30 tool calls a month
No card required. Connect Google Ads, Meta Ads, GA4 or Search Console and ask Claude for the outcome — it picks the tool.