Skip to main content
Glama

Caybl

by ai.caybl.api
OverviewDiscussionsAdmin

Change a keyword's status or bid, or remove it

update_keyword
Destructive

Change an existing keyword's status (PAUSED/ENABLED, or REMOVED to delete it permanently) and/or its max CPC bid. add_keywords can only add new keywords - this is how to act on one that's already there, e.g. pausing an underperformer found via get_search_terms.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cpcBidNoNew max CPC in account currency.
statusNoREMOVED is permanent.
adGroupIdYesAd group id the keyword belongs to.
keywordIdYesKeyword's criterion id, e.g. from add_keywords' resourceNames or a GAQL query on ad_group_criterion.
customerIdNo10-digit Google Ads customer id. Omit only if this connection has exactly one reachable account - with more than one, omitting it errors and lists the available ids to pick from.
extraFieldsNoEscape hatch for a field Google requires that this tool doesn't set yet - use it when a prior call to this same tool failed naming a required field and its valid values (e.g. after adding `contains_eu_political_advertising`, retry with { contains_eu_political_advertising: "DOES_NOT_CONTAIN_EU_POLITICAL_ADVERTISING" }). Keys are the Ads API's own snake_case field names; nest an object to add a field under one this tool already sets (e.g. a new network_settings sub-field). Only ADDS fields not already set by this tool's own arguments - it can never override `status` or any other field already set here, so it cannot be used to bypass validation or a safety default like a campaign's PAUSED-by-default status.
validateOnlyNoDry run. When true the Google Ads API validates the change and reports any errors but applies nothing. Use this first whenever you are unsure - it is free and cannot affect spend.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description reinforces that REMOVED is a permanent delete, adding useful context beyond the enum, but says little about irreversibility of bids or idempotency beyond what annotations and schema provide.

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?

Two tight sentences, front-loaded with the core action and followed by the sibling routing. No filler.

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 destructive mutation tool, the safety semantics are carried by annotations, all seven parameters are documented at 100% coverage, and the description supplies the routing and permanence caveat. No output schema is needed and nothing an agent requires to call correctly is missing.

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 100%, so every parameter (including validateOnly, extraFields, customerId) is already fully documented in the schema. The description only echoes the status/bid fields, adding no syntax or constraint detail beyond it.

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?

Specific verb+resource ('Change an existing keyword's status...and/or its max CPC bid') with the exact mutation fields named. It explicitly distinguishes itself from the sibling add_keywords by stating add_keywords only adds while this acts on existing keywords.

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

Usage Guidelines5/5

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

Routes the agent precisely: it names add_keywords as the alternative for creation and supplies a concrete when-to-use scenario ('pausing an underperformer found via get_search_terms'). Nothing about selecting this tool vs. siblings is left to inference.

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

All Caybl toolsInspect
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