Google Ads MCP Server

add_demographic_targets

Add age and gender targeting to Google Ads ad groups by specifying demographics and bid modifiers to refine audience reach.

Instructions

Add age/gender targeting

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>",
      "adGroupId": "<adGroupId>",
      "demographics": "<demographics>"
    },
    "name": "add_demographic_targets"
  }
}

Input Schema

Name	Required	Description
`adGroupId`	Yes	Ad group ID
`customerId`	Yes	Google Ads customer ID
`demographics`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

C2.2/5.0

Behavior1/5

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

There are no annotations, and the description does not disclose any behavioral traits. It does not mention whether existing demographic targets are overwritten, permission requirements, or effects on bidding. The description carries the full burden for behavioral transparency and fails completely.

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

Conciseness2/5

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

The description is a single sentence, which is concise, but it is under-specified for a tool with three parameters and a nested object. It provides no structure or details, making it insufficient rather than optimally concise.

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

Completeness1/5

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

Given the tool has no annotations, no output schema, and a nested demographics object, the description is grossly incomplete. It lacks usage context, behavioral details, and parameter semantics, leaving the agent with insufficient information to invoke the tool correctly.

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?

The schema covers two of three parameters with descriptions, and the description says 'age/gender targeting,' which loosely maps to the demographics array. However, it adds minimal meaning about gender/ageRange values or bidModifier, and does not compensate for the nested object's lack of documentation.

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

Purpose4/5

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

The description uses the verb 'Add' with the resource 'age/gender targeting', which clearly indicates the tool's function. It distinguishes from sibling tools like add_location_targets and manage_language_targets. However, it omits the ad group scope, which is present in the schema.

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?

The description provides no guidance on when to use this tool versus alternatives, no exclusions, and no prerequisites. It only states the obvious action, offering no additional decision-making context.

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

Deploy Server