Skip to main content
Glama

google_ads_location_targeting_list

List all location targeting criteria from a Google Ads campaign, including criterion IDs, geo target constants, and bid modifiers. Useful for reviewing current location settings before making changes.

Instructions

List every LOCATION campaign_criterion on a Google Ads campaign. Returns [{criterion_id, geo_target_constant (resource path, e.g. 'geoTargetConstants/2392' for Japan), bid_modifier (float or null)}]. Read-only. Geo target constant IDs map to countries/regions/cities — look up via Google's GeoTargetConstantService. For adding or removing locations use google_ads_location_targeting_update; for schedule-based targeting use google_ads_schedule_targeting_list.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
customer_idNoGoogle Ads customer ID as a 10-digit string without dashes (e.g. '1234567890'). Optional — falls back to GOOGLE_ADS_CUSTOMER_ID / GOOGLE_ADS_LOGIN_CUSTOMER_ID from the configured credentials when omitted.
campaign_idYesCampaign ID as a numeric string without dashes (e.g. '23743184133'). Obtain via google_ads_campaigns_list.
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description fully discloses behavior: it is read-only, returns a structured list of criteria, and explains the mapping to geo target constants. No hidden side effects or contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise (4 sentences) and front-loaded with the core action. Every sentence adds value: purpose, output format, read-only note, geo lookup reference, and sibling tool guidance. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a list tool with no output schema, the description sufficiently covers return structure, read-only nature, and related tools. It also provides actionable guidance for interpreting results (GeoTargetConstantService). Complete within context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description does not add parameter semantics beyond what the schema already provides (e.g., fallback behavior for customer_id is already in schema). No additional clarification needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it lists every LOCATION campaign_criterion on a Google Ads campaign, specifies the return format, and distinguishes from sibling tools (update and schedule). It uses a specific verb('List') and resource, making the purpose unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly notes the tool is read-only and provides direct references to alternative tools for adding/removing locations (google_ads_location_targeting_update) and schedule-based targeting (google_ads_schedule_targeting_list). It also explains how to interpret return values via GeoTargetConstantService.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/logly/mureo'

If you have feedback or need assistance with the MCP directory API, please join our Discord server