Skip to main content
Glama
logly

mureo

by logly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

google_ads_location_targeting_update

Add or remove location criteria on a Google Ads campaign in a single mutate. Returns one resource name per executed operation (adds first, then removes).

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
reasonNoWhy this change is being made: one or two sentences naming the evidence and the expected effect. Stored in the journal and on the action_log entry this call produces, for the operator and the next session.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.20.0
    • addedInput schema / properties / reason
      Added value: +{
+  "description": "Why this change is being made: one or two sentences naming the evidence and the expected effect. Stored in the journal and on the action_log entry this call produces, for the operator and the next session.",
+  "maxLength": 500,
+  "type": "string"
+}
  2. Changed2 schema fields changedv0.10.37
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / anyOf
      Added value: +[
+  {
+    "required": [
+      "add_locations"
+    ]
+  },
+  {
+    "required": [
+      "remove_criterion_ids"
+    ]
+  }
+]
  3. Addedv0.10.11
  4. Removedv0.10.9
  5. Addedv0.9.12
  6. Removedv0.9.6
  7. Addedv0.9.2
  8. Removedv0.9.1
  9. Addedv1.0.5

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden. It explicitly states 'Mutating' and explains the return format, the order of operations (adds first, then removes), and reversibility. It also discloses the auto-prefixing behavior for bare IDs. This is transparent and leaves no ambiguity about side effects.

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 about three sentences, front-loads the purpose, then covers return format, mutation, reversibility, and input requirements. Every sentence earns its place with no fluff or repetition. It is well-structured and easy to parse.

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 mutating tool with 5 parameters, some optional, an anyOf constraint, and no output schema, the description covers the essential behavior: return format, operation order, reversibility, input requirements, and ID format handling. It does not describe error cases, but given the schema covers parameter descriptions and the tool is fairly straightforward, this is complete enough for an agent to invoke it correctly.

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?

Schema description coverage is 100%, so the baseline is 3. The description adds value by clarifying the return format and reiterating the bare-ID auto-prefix behavior (also in the schema). It reinforces the anyOf constraint (at least one of add_locations/remove_criterion_ids) which is present in the schema but is helpful to state in prose. It does not add entirely new semantics but supplements the schema.

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 the action: 'Add and/or remove location criteria on a Google Ads campaign in a single mutate.' It specifies the resource (location criteria on a campaign) and the verb (add/remove), and distinguishes it from sibling tools like device_targeting or schedule_targeting. The single-mutate behavior is a key differentiator.

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 gives practical usage constraints: at least one of add_locations/remove_criterion_ids must be provided, and it notes that the operation is reversible only by calling the tool again with inverse operations. It does not explicitly name alternative tools (e.g., google_ads_location_targeting_list for viewing), but the schema does that for remove_criterion_ids. The purpose is clear enough that an agent can infer when to use it.

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

Deploy Server

Other Tools