Skip to main content
Glama
Google Workspace MCP connector

Google Workspace MCP connector

by animesh-ex

ads_set_status

Destructive

Pause or enable Google Ads campaigns, ad groups, ads, or keywords by setting status to PAUSED or ENABLED. Supports dry-run validation and restores spend when re-enabled.

Instructions

Pause or enable campaigns, ad groups, ads or keywords. ENABLED resumes spending. Use validateOnly=true to dry-run. Always confirm with the user first.

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>",
      "entity": "<entity>",
      "ids": "<ids>",
      "status": "<status>"
    },
    "name": "ads_set_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYescampaign/ad group IDs; for ad: 'adGroupId~adId'; for keyword: 'adGroupId~criterionId'
entityYes
statusYes
customerIdYesGoogle Ads customer ID (with or without dashes)
validateOnlyNo
loginCustomerIdNoManager (MCC) ID if accessing through a manager; defaults to ads.json

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare destructive=true and openWorld=true, so the safety bar is partly met. The description does add real behavioral context: that ENABLED resumes spending (a cost consequence) and that validateOnly enables a dry run. It stops short of saying whether the call is reversible, what a partial batch failure looks like, or what permissions are required.

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?

Three short sentences, action first, safety instructions last, with zero filler. Every sentence carries information an agent needs before calling a destructive mutation.

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 6-parameter mutation with no output schema, the description covers the essentials: what changes, the spending side effect, the dry-run path, and the need to confirm. Remaining gaps (permissions, partial-failure behavior, batched ids semantics) are modest rather than blocking.

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 coverage is 50%, with entity, status, and validateOnly undocumented in the schema. The description compensates for two of these (status consequence, validateOnly dry-run) and the entity enum is self-explanatory, but it adds no batching semantics for the multi-value ids array. Adequate but not full compensation.

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 pair ('Pause or enable') plus the exact resource set (campaigns, ad groups, ads, keywords), which maps 1:1 to the entity enum. It is clearly distinguishable in kind from budget-setting or performance siblings, though it never names an alternative tool explicitly.

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?

Gives two concrete operating instructions: use validateOnly=true to dry-run, and always confirm with the user first. That covers a prerequisite and a safe-practice path, but offers no guidance on when to choose this tool over a related one (e.g. budget changes vs status changes).

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