Skip to main content
Glama
ibrahimhajjaj

seo-console-mcp

ads_update

Change Google Ads bids, budgets, or statuses. Safely dry-run changes, check guards, and confirm updates to prevent overspending.

Instructions

Change one Google Ads keyword bid, campaign daily budget, campaign status, ad status or keyword status. Pausing one keyword is its own kind because dropping a bid is not the same thing: the keyword stays eligible and goes on competing for the same budget. Spends money, so it is a dry run unless dryRun is false, it refuses a change that trips a guard unless confirm is true, and it re-reads the value after writing because an accepted request is not a stored value. Guards: more than three times the current amount, more than $25, or pausing something that is serving

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindYesWhat to change: a keyword's max CPC bid, a campaign's daily budget, a campaign's status, an ad's status, or a keyword's status. Use keywordStatus to stop one keyword serving; dropping its bid is not the same thing, because the keyword stays eligible and keeps competing for the same budget
valueYesThe new amount in dollars for a bid or budget, or pause or enable for a status
dryRunNoReport what would change and which guards it trips, without changing anything. On by default: this tool spends money, so performing a change has to be asked for
targetYesThe keyword text, the campaign name, or the numeric ad id. It must match exactly one thing or the call is refused
confirmNoPerform a change that trips a guard. Ignored on a dry run. The dry run lists the guard reasons, so this confirms something already read rather than something unseen

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindYes
noOpYes
afterYes
beforeYes
guardsYes
targetYes
appliedYes
matchesYesWhether the re-read value equals what was sent
readBackYesThe value re-read from the account after the write. An accepted request is not proof of a stored value
customerIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.18.0

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations provided, the description carries full burden of behavioral disclosure. It explicitly states the tool spends money, defaults to a dry run, requires confirm to override guards, and re-reads values after writing because an accepted request may not be a stored value. It also enumerates the guard conditions, making the behavior fully transparent.

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?

The description is dense and covers multiple aspects, but it is not excessively long. It front-loads the purpose and then explains nuanced behaviors. While it could be structured more clearly with separate sentences for each behavioral note, it remains concise enough and each clause adds value.

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?

The description is comprehensive for a tool with this complexity. It covers the dry run behavior, guard conditions, confirmation requirement, and the distinction between bid and status changes. Since an output schema exists, the description need not explain return values, and nothing critical is missing for an agent to call this tool correctly.

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 100%, so parameters are well-documented. The description adds meaningful context beyond the schema, explaining the relationship between bid and status, and the semantics of dryRun and confirm. It clarifies that dryRun is on by default and why, which is not evident from the schema alone.

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?

The description clearly states the tool's function: changing one specific ads entity (bid, budget, status). It also distinguishes between changing a bid and pausing a keyword, which differentiates it from sibling tools that might do similar actions. The resource is specified exactly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use this tool (for single changes) and clarifies that pausing a keyword is distinct from lowering its bid. However, it does not explicitly name alternative tools like ads_update_batch or ads_negatives_update, leaving the when-not-to-use guidance implicit rather than explicit.

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