Google Ads MCP Server

set_campaign_status

DestructiveIdempotent

Change a Google Ads campaign's status to enabled, paused, or removed. Pausing applies immediately; enabling or removing requires a preview and confirmation.

Instructions

Set a campaign's status (enable, pause, or remove).

Safety: PAUSED is applied immediately (it stops spend). ENABLED and REMOVED
return a preview first; call again with confirm=True to apply.

Args:
    customer_id: Google Ads customer ID.
    campaign_id: Campaign ID.
    status: New status -- 'ENABLED', 'PAUSED', or 'REMOVED'.
    confirm: Must be True to enable or remove.

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>",
      "status": "<status>"
    },
    "name": "set_campaign_status"
  }
}

Input Schema

Name	Required	Description	Default
`status`	Yes
`confirm`	No
`campaign_id`	Yes
`customer_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 11, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Adds substantive behavior beyond the annotations: the preview-then-confirm gate for enable/remove and the immediate-apply semantics for pause, including that pausing stops spend. This is exactly the kind of irreversible-action context an agent needs before calling a destructive mutation, and it is consistent with destructiveHint=true.

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-loads the action and the safety rule before the arg list, and every sentence carries information. The Args block is slightly redundant with the safety paragraph on `confirm`, but that repetition reinforces the two-step flow rather than wasting space.

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?

Given a destructive, open-world mutation with no output schema and no schema descriptions, the definition covers the mutation semantics, the safety gate, and parameter meanings. An agent could invoke it correctly on the first attempt without further clarification.

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

Parameters5/5

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

Schema coverage is 0%, and the description compensates fully by documenting all four parameters, including the enum values for status (which the schema leaves as a bare string) and the exact precondition for confirm. It adds meaning the schema cannot convey on its own.

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?

States a specific verb (set) and resource (a campaign's status) and enumerates the exact three accepted values, so an agent knows precisely what the tool mutates. The scope is unambiguous against similarly named siblings like set_ad_group_status and set_ad_status because the resource is named as campaign.

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?

Clearly explains the operational flow: PAUSED applies immediately, whereas ENABLED and REMOVED require a second call with confirm=True. It does not address overlap with the sibling remove_campaign, leaving the agent to guess which removal path to choose.

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

Deploy Server