Google Ads MCP Server

add_location_targets

Add geographic targeting to Google Ads campaigns by specifying location IDs and optional bid modifiers.

Instructions

Add geographic targeting to campaigns

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "customerId": "<customerId>",
      "campaignId": "<campaignId>",
      "locations": "<locations>"
    },
    "name": "add_location_targets"
  }
}

Input Schema

Name	Required	Description
`locations`	Yes
`campaignId`	Yes	Campaign ID
`customerId`	Yes	Google Ads customer ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations, the description carries the full burden. It does not disclose whether adding targets appends or replaces existing targeting, or any side effects, permissions, or limitations. The verb 'add' is the only behavioral hint.

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 a single, front-loaded sentence that is concise and free of filler. Every word is relevant to the purpose.

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

Completeness2/5

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

For a mutation tool with no annotations or output schema, the description is too sparse. It fails to explain expected behavior (append vs replace), required campaign existence, or any operational context, making it incomplete for an agent to invoke confidently.

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

Parameters2/5

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

Schema coverage is 67% but the critical 'locations' parameter lacks description. The tool description adds no parameter-level meaning, leaving the structure and semantics of location objects (e.g., bidModifier) unexplained.

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), resource (geographic targeting), and target (campaigns). It differentiates from sibling tools like add_demographic_targets and set_location_bid_adjustments by the specific object type.

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

Usage Guidelines2/5

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

No guidance is provided about when to use this tool versus alternatives, prerequisites, or exclusions. The description simply states what it does without contextualizing the use case.

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

Deploy Server