AdCopilot

Google Ads: update keyword status or bid

update_keyword

DestructiveIdempotent

Updates a keyword's status or bid.

It never deletes: status REMOVED is refused. PAUSED stops the keyword
serving and ENABLED switches it back on.

Args:
    customer_id: The Google Ads customer ID (numbers only, no hyphens).
    ad_group_id: The ID of the ad group containing the keyword.
    criterion_id: The criterion ID of the keyword.
    status: New status. One of: ENABLED, PAUSED. Optional.
    cpc_bid_micros: New CPC bid in micros of the account's currency. Optional.

Returns:
    Dictionary with the updated resource name and confirmation message.

Tools revision: 5c9bea8f.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`status`	No
`ad_group_id`	Yes
`customer_id`	Yes
`criterion_id`	Yes
`cpc_bid_micros`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.8/5.0

Behavior5/5

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

The annotations already declare mutation, open-world, idempotent, and destructive behavior. The description adds valuable non-obvious behavior: REMOVED is refused, PAUSED stops serving, ENABLED resumes serving, and the return includes the updated resource name.

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?

The description is front-loaded, structured into purpose, behavioral constraints, Args, and Returns. Every sentence adds useful information without redundancy.

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?

For a mutation tool with rich annotations and an output schema, the description covers purpose, update constraints, parameter meanings, and return shape. An agent has enough information to invoke it correctly.

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 description coverage is 0%, so the description carries the full burden. It documents all five parameters, including customer ID formatting, the allowed status values, optionality, and that cpc_bid_micros is in micros of the account currency.

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 states a specific verb and resource: update a keyword's status or bid. This clearly distinguishes it from creation tools such as add_keywords and from ad-group or campaign updates.

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?

It gives clear usage context and an explicit when-not: status REMOVED is refused because the tool never deletes. It does not name a specific alternative tool for deletion, so it falls short of fully explicit alternative routing.

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

All AdCopilot tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?