Skip to main content
Glama
Sign In
Google Ads MCP Server

Google Ads MCP Server

by nexoradev-stack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

set_ad_status

DestructiveIdempotent

Change a Google Ads ad to enabled, paused, or removed status; paused applies immediately, while enabling or removing returns a preview requiring confirmation.

Instructions

Set an ad's status (enable, pause, or remove).

Safety: PAUSED applies immediately; ENABLED and REMOVED return a preview
first and need confirm=True.

Args:
    customer_id: Google Ads customer ID.
    ad_group_id: Ad group ID containing the ad.
    ad_id: Ad ID.
    status: New status -- 'ENABLED', 'PAUSED', or 'REMOVED'.

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>",
      "ad_group_id": "<ad_group_id>",
      "ad_id": "<ad_id>",
      "status": "<status>"
    },
    "name": "set_ad_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
ad_idYes
statusYes
confirmNo
ad_group_idYes
customer_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the description's real contribution is the disclosed two-step preview/confirm protocol for ENABLED and REMOVED, which an agent could not infer from the schema. It leaves gaps on what the preview returns and whether REMOVED is permanent or recoverable.

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?

Purpose is front-loaded in one line, safety behavior follows, and the Args block is compact. The Args entries for the three IDs add little beyond their names, but at 0% schema coverage that redundancy is defensible.

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

Completeness4/5

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

For a destructive, open-world mutation with no output schema, the definition covers the essential unknown (the preview/confirm gate) and all required arguments. Missing only post-removal consequences and what the preview payload looks like.

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

Parameters3/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 carry parameter meaning; it documents the three ID parameters and supplies the status vocabulary ('ENABLED', 'PAUSED', 'REMOVED') that the schema lacks as an enum, and explains confirm via the safety note. However no ID format examples or hint about which account scope the IDs belong to are given, so compensation is partial rather than complete.

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?

States a specific verb and resource ('Set an ad's status') and enumerates the three target states, which makes it distinguishable from set_ad_group_status and set_campaign_status purely by the resource noun. It stops short of explicitly naming those siblings, but the target is unambiguous.

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?

The Safety line tells the agent exactly how to invoke each status path: PAUSED applies directly, while ENABLED and REMOVED require a confirm=True follow-up. This is clear procedural guidance, though it does not say when an agent should prefer this tool over a broader update path or when a status change should be avoided.

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