Skip to main content
Glama

Honeyfield Marketing MCP

Google Ads: Update keyword bid

ads_update_keyword_bid
Destructive

CPC Gebot eines Keywords ändern (in EUR, auf ganze Micros gerundet). Wirkt nur bei Kampagnen mit MANUAL_CPC (siehe bidding_strategy in ads_list_campaigns); bei Smart Bidding wird das Gebot gespeichert, aber nicht für die Auslieferung verwendet. cpc_bid_eur muss > 0 sein, sonst {'error': 'invalid_amount'} und nichts wird geändert. workspace: Slug des Kunden-Workspace (optional bei nur einem Workspace).

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": {
      "ad_group_id": "<ad_group_id>",
      "criterion_id": "<criterion_id>",
      "cpc_bid_eur": "<cpc_bid_eur>"
    },
    "name": "ads_update_keyword_bid"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspaceNo
ad_group_idYes
cpc_bid_eurYes
criterion_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, so the description is not carrying the safety burden alone, yet it still adds substantial behavior: micros rounding, EUR currency, the 'invalid_amount' rejection path and the guarantee that nothing changes on error. It does not cover required permissions or whether the previous bid is recoverable, which keeps it off a 5.

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 action and unit are front-loaded and each following sentence carries a distinct constraint (MANUAL_CPC scope, validation rule, workspace fallback) with no filler. Density is high but nothing is redundant.

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?

With an output schema present and annotations covering mutation/open-world traits, the description supplies what the structured fields do not: unit, rounding, validation failure, and bidding-strategy caveat. The remaining gap is the meaning of the two identifier parameters a caller must supply.

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 0%, so the description must compensate, and it does so for two of four parameters: cpc_bid_eur (must be > 0, EUR, rounded to micros) and workspace (optional when there is only one workspace). ad_group_id and criterion_id remain unexplained and must be inferred from the name.

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 opening sentence gives a precise verb+resource pair ('CPC Gebot eines Keywords ändern') and pins down the unit (EUR, micros). The keyword-level scope is enough to separate it from ads_update_ad_group_bid and from the status-only siblings such as ads_update_keyword_status.

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 states an explicit precondition – only effective for MANUAL_CPC campaigns – and routes the agent to ads_list_campaigns to check bidding_strategy. It also says what happens under Smart Bidding (bid stored but unused), which is real when/when-not guidance. It stops short of naming an alternative tool for the non-MANUAL_CPC case.

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