Skip to main content
Glama
logly

mureo

by logly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

google_ads_keywords_add

Add keywords to a single Google Ads ad group with match type (broad, phrase, exact) and get created criterion IDs. Check for duplicates across ad groups beforehand to prevent rejection.

Instructions

Adds one or more keyword criteria to a single ad group. Returns the created criterion_ids keyed by their input position. Mutating — not automatically reversible; record before-state with mureo_state_action_log_append if you may need to roll back. Duplicate text+match_type pairs inside the same ad group are rejected by Google Ads — call google_ads_keywords_cross_adgroup_duplicates first if you are adding at scale.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
reasonNoWhy this change is being made: one or two sentences naming the evidence and the expected effect. Stored in the journal and on the action_log entry this call produces, for the operator and the next session.
keywordsYesKeywords to add. Each item has `text` (required) and optional `match_type` (BROAD / PHRASE / EXACT, default BROAD).
ad_group_idYesTarget ad group ID. All keywords in this call are added to this single ad group.
customer_idNoGoogle Ads customer ID as a 10-digit string without dashes (e.g. '1234567890'). Optional — falls back to GOOGLE_ADS_CUSTOMER_ID / GOOGLE_ADS_LOGIN_CUSTOMER_ID from the configured credentials when omitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.20.0
    • addedInput schema / properties / reason
      Added value: +{
+  "description": "Why this change is being made: one or two sentences naming the evidence and the expected effect. Stored in the journal and on the action_log entry this call produces, for the operator and the next session.",
+  "maxLength": 500,
+  "type": "string"
+}
  2. Changed1 schema field changedv0.10.37
    • addedInput schema / additionalProperties
      Added value: +false
  3. Addedv0.10.11
  4. Removedv0.10.9
  5. Addedv0.9.12
  6. Removedv0.9.6
  7. Addedv0.9.2
  8. Removedv0.9.1
  9. Addedv1.0.5

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description carries the full behavioral disclosure burden. It clearly states this is mutating, not automatically reversible, suggests recording before-state for rollback, explains the return mapping, and discloses the duplicate rejection behavior. This is exemplary transparency for a mutation tool.

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?

Three sentences deliver the core action, return contract, mutation warning, rollback guidance, and a critical prerequisite. Every sentence earns its place, and the most important facts are front-loaded. No filler or redundant restatement of the schema.

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 no output schema and no annotations, this description covers the action, scope, return value, irreversibility, rollback path, and the key API constraint. The parameter schemas are already rich, so nothing essential is missing for an agent to invoke this correctly.

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 the schema already documents ad_group_id, keywords, customer_id, and reason in detail. The description adds contextual behavior about duplicates and rollback, but it does not materially enrich the per-parameter meaning beyond what the schema already provides. Baseline 3 is appropriate.

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 names a specific verb and resource ('Adds one or more keyword criteria to a single ad group'), and clearly distinguishes this from sibling tools like google_ads_keywords_remove, google_ads_keywords_pause, and google_ads_negative_keywords_add. It also states the return value (criterion_ids keyed by input position), making the tool's purpose unambiguous.

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?

The description explicitly tells the agent when a prerequisite check is needed: call google_ads_keywords_cross_adgroup_duplicates first when adding at scale due to Google Ads rejecting duplicate text+match_type pairs. It also signals the mutation context and rollback recording step with mureo_state_action_log_append, which helps the agent decide how to use this tool safely.

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

Deploy Server

Other Tools