Google Ads MCP Server

list_ad_groups

Read-only

Retrieve and list ad groups within a specific Google Ads campaign, with optional status filtering and a limit on results to review targeting structure.

Instructions

List ad groups in a campaign.

Args:
    customer_id: Google Ads customer ID.
    campaign_id: Campaign ID to list ad groups for.
    status_filter: Optional -- 'ENABLED', 'PAUSED', or 'REMOVED'.
    limit: Max ad groups to return (default 100).

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": {
      "customer_id": "<customer_id>",
      "campaign_id": "<campaign_id>"
    },
    "name": "list_ad_groups"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`campaign_id`	Yes
`customer_id`	Yes
`status_filter`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 11, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered by structured data. The description adds the default limit of 100 and the accepted status values, but is silent on pagination/truncation behavior and on whether a null status_filter includes REMOVED entities by default — a meaningful ambiguity for a listing tool.

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?

Front-loaded with a one-line purpose statement, then a compact Args block with no filler. The Args entries restate parameter names but each adds at least one useful detail (allowed values, default), so little is wasted.

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

Completeness3/5

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

For a read-only, four-parameter listing tool with no output schema, the definition is adequate but leaves the agent guessing about result ordering, pagination beyond limit, and whether missing/REMOVED ad groups appear by default. Those gaps matter for a tool whose whole job is enumeration.

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?

With 0% schema description coverage and no enums in the schema, the description carries the full burden and does document all four parameters, including the concrete values 'ENABLED'/'PAUSED'/'REMOVED' for status_filter and the default of 100 for limit. The only shortfall is that customer_id and campaign_id are described only tautologically.

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 opens with a specific verb+resource ("List ad groups") and narrows the scope to "in a campaign", which distinguishes it from account-wide listings. It does not, however, contrast itself with siblings like get_ad_group or list_ads, so the differentiation stops short of a 5.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer you call this when you want the ad groups belonging to one campaign. There is no explicit guidance on when to prefer this over get_ad_group or list_ads, nor any stated prerequisites (e.g., that campaign_id must belong to customer_id).

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

Deploy Server