Skip to main content
Glama
Sign In
Google Ads MCP Server

Google Ads MCP Server

by MaxGhenis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

pause_ad_group

Pause an active ad group in Google Ads by specifying its ID. Optionally validate the action without execution using a dry run.

Instructions

Pause an ad group.

Args: ad_group_id: Ad group ID to pause customer_id: Target customer ID (optional if set in config) dry_run: If True, validate but don't execute

Returns: Result with success status

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": {
      "ad_group_id": "<ad_group_id>"
    },
    "name": "pause_ad_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
ad_group_idYes
customer_idNo
dry_runNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It mentions 'dry_run' for validation without execution and returns a success status. However, it does not describe side effects, required permissions, or what happens to the ad group if paused (e.g., active campaigns, lapsing).

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?

Extremely concise and well-structured. The purpose is stated in one line, followed by clear parameter descriptions in Args format, and a Returns line. No unnecessary words.

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 simple mutation tool with 3 parameters and an output schema, the description covers purpose, parameters, and return value. However, it lacks usage guidelines and behavioral context. With no annotations, it is minimally viable but not fully 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?

Schema description coverage is 0%, so the description must compensate. It explains each parameter: ad_group_id (required), customer_id (optional with config hint), and dry_run (validation mode). This adds meaningful context beyond the schema definition.

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 clearly states the verb and resource ('Pause an ad group'). It distinguishes from sibling tools like 'enable_ad_group' and 'create_ad_group'. However, it does not differentiate from 'pause_campaign' or clarify any special scope.

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 on when to use this tool versus alternatives like 'enable_ad_group' or 'pause_campaign'. No prerequisites or context for when pausing is appropriate.

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