Skip to main content
Glama

set_google_campaign_status

Pause or Enable a live Google Ads campaign.

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": {
      "campaignId": "<campaignId>",
      "status": "<status>"
    },
    "name": "set_google_campaign_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusYes
campaignIdYesNumeric Google Ads campaign ID.
customerIdNo
loginCustomerIdNo
confirmLiveSpendNoRequired when setting status to ENABLED to confirm live ad spending on Google Ads.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / confirmLiveSpend
      Added value: +{
      +  "description": "Required when setting status to ENABLED to confirm live ad spending on Google Ads.",
      +  "type": "boolean"
      +}
  2. Added

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden and does not meet it. It never discloses that enabling starts live ad spend (the confirmLiveSpend gate in the schema), whether the change is reversible, what permissions the customerId/loginCustomerId require, or what happens on a paused-vs-enabled mismatch.

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?

A single front-loaded sentence with zero filler, which is structurally clean. However, the brevity edges into under-specification for a live-spend mutation, so it is efficient rather than exemplary.

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

Completeness2/5

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

A 5-parameter write tool with no annotations, no output schema, and 40% schema coverage needs considerably more description. The critical live-spend confirmation requirement and account-context parameters are absent, leaving an agent likely to call it incorrectly on the ENABLED path.

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

Parameters2/5

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

Schema coverage is only 40%, so the description needed to compensate and does not. It adds no meaning for campaignId, customerId, or loginCustomerId, and importantly omits any mention of confirmLiveSpend being mandatory for ENABLED — a param whose description alone may be skimmed past.

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?

"Pause or Enable a live Google Ads campaign" names a specific verb pair and resource, so an agent immediately knows the operation and the platform. It is distinguishable from set_microsoft_campaign_status by the Google Ads scope, though the description never explicitly states that differentiation.

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?

There is no guidance on when to choose this over siblings such as update_google_campaign_budget or publish_campaign_to_google_ads, and no prerequisites are stated. The word "live" weakly implies the campaign must already be published, but that is left to inference rather than stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources