Skip to main content
Glama

google_ads_location_targeting_update

Update location targeting on a Google Ads campaign by adding new locations and removing existing criteria in one operation.

Instructions

Add and/or remove location criteria on a Google Ads campaign in a single mutate. Returns [{resource_name}] — one entry per operation executed (adds first, then removes). Mutating — adds create new criteria, removes delete them by criterion_id. Reversible only by calling this tool again with the inverse operations. At least one of add_locations / remove_criterion_ids must be provided. Locations can be passed as bare numeric IDs or as full 'geoTargetConstants/' paths; bare IDs are auto-prefixed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
campaign_idYesCampaign ID as a numeric string without dashes (e.g. '23743184133'). Obtain via google_ads_campaigns_list.
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.
add_locationsNoGeo target constants to add, either as numeric IDs (e.g. '2392' for Japan, '2840' for US) or as full resource paths ('geoTargetConstants/2392'). Bare IDs are auto-prefixed.
remove_criterion_idsNoExisting criterion_ids to remove (numeric strings, e.g. '30002'). Obtain via google_ads_location_targeting_list.
Behavior4/5

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

With no annotations, the description carries the burden. It discloses mutability, reversibility only by inverse operations, auto-prefixing of bare IDs, and return format. It does not mention permission requirements or rate limits, but covers the key behavioral traits comprehensively.

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

Conciseness4/5

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

The description is concise at 4 sentences, front-loading the primary purpose. It is structured logically: purpose, return format, mutability, conditions, formatting details. No wasted words.

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

Completeness4/5

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

The description explains the return value (array of resource names) and execution order (adds then removes). It covers essential aspects for a mutation tool without output schema. Missing details like error handling for invalid IDs, but given moderate complexity, it is reasonably complete.

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

Parameters4/5

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

The schema has 100% coverage, but the description adds significant value by clarifying that bare IDs are auto-prefixed to full paths, providing examples (e.g., Japan, US), and specifying the format of criterion_ids. This goes beyond the schema descriptions.

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 specifies the verb (add/remove) and resource (location criteria on a campaign) and distinguishes from sibling tools like google_ads_location_targeting_list. It clearly states the action in a single mutate.

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

Usage Guidelines4/5

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

The description provides clear context, stating that at least one of add_locations or remove_criterion_ids must be provided, and explains how to obtain IDs via sibling tools. It does not explicitly list when not to use this tool versus alternatives, which prevents a perfect score.

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