Skip to main content
Glama

Honeyfield Marketing MCP

Google Ads: Add keyword

ads_add_keyword

Keyword zu einer Ad Group hinzufügen. Match Type: BROAD, PHRASE oder EXACT. Default Status: PAUSED (Safety — User muss manuell aktivieren). Ein Keyword in einer laufenden Ad Group gibt sofort Geld aus — der direkteste Weg zu ungewolltem Werbebudget im ganzen Toolset. Beim Ergänzen bestehender, laufender Ad Groups deshalb daran denken: das Keyword wirkt erst nach ads_update_keyword_status(..., 'ENABLED'). Wer bewusst sofort ausspielen will, gibt status='ENABLED' mit. cpc_bid_eur wirkt nur bei MANUAL_CPC-Kampagnen; bei Smart Bidding ohne Effekt auf die Auslieferung. 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>",
      "keyword": "<keyword>"
    },
    "name": "ads_add_keyword"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusNoPAUSED
keywordYes
workspaceNo
match_typeNoBROAD
ad_group_idYes
cpc_bid_eurNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnly=false, destructive=false) by explaining that a keyword in a live ad group starts spending immediately and only takes effect after an explicit status update — real side-effect disclosure for a mutation tool. It also notes cpc_bid_eur is a no-op under Smart Bidding, which prevents a silent misconfiguration.

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?

Front-loaded with the action and defaults, then the reasoning; every clause is actionable. Some rhetorical flourish about spending money could be trimmed, but the emphasis is on point for a spend-risk mutation.

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?

For a 6-parameter mutation with an output schema, the definition covers defaults, side effects and the follow-up tool, so an agent can call it correctly. Missing pieces are minor: no pointer to ads_bulk_add_keywords for multi-keyword insertion and no keyword string format guidance.

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?

With 0% schema description coverage the description must carry the burden, and it does for match_type (BROAD/PHRASE/EXACT), status (default PAUSED, override ENABLED), cpc_bid_eur (MANUAL_CPC only) and workspace (optional with a single workspace). It says nothing about ad_group_id or the expected keyword string format (e.g., whether bracketed/exact syntax is accepted).

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?

States a specific verb and resource ('Keyword zu einer Ad Group hinzufügen') plus the allowed match types, so the agent knows exactly what is created and where. It is distinguishable from read-only siblings like ads_list_keywords and from ads_remove_keyword.

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?

Gives clear conditional guidance: default PAUSED for safety, enable later via ads_update_keyword_status(..., 'ENABLED'), or pass status='ENABLED' deliberately. It does not mention the sibling ads_bulk_add_keywords, so the single-vs-bulk decision 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources