Skip to main content
Glama
logly

mureo

by logly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

google_ads_ad_groups_update

Modify ad group settings (name, status, CPC bid) via partial update; only provided fields change and the updated ad group is returned. Note: changes aren't automatically reversible.

Instructions

Updates one or more settings on an existing ad group. Partial update — only provided fields are changed. Returns the updated ad group. Mutating — not automatically reversible; record before-state with mureo_state_action_log_append if you may need to roll back. Does not cascade to ads or keywords under this ad group; use google_ads_ads_update / update_status and google_ads.keywords.* for those.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoNew ad group name (max 255 chars).
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.
statusNoNew status. For status-only changes this tool is equivalent to setting the status field alone — there is no separate ad_groups.update_status call.
ad_group_idYesAd group ID to update.
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.
cpc_bid_microsNoNew default CPC bid in micros (1_000_000 micros = 1 unit of account currency).

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.9/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 burden, and it excels. It explicitly warns 'Mutating — not automatically reversible; record before-state with mureo_state_action_log_append if you may need to roll back.' It also discloses that the update is partial and does not cascade, which are critical behavioral traits. It does not mention auth or rate limits, but the rollback guidance and scope warnings are substantial.

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 concise yet dense. It opens with the core purpose and partial update behavior, then addresses cascading and rollback in clear sentences. Every sentence adds unique value with no filler. The structure is logical: purpose → behavior → exclusions → rollback guidance.

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 6 parameters, no output schema, and no annotations, this description is remarkably complete. It covers what changes, how partial updates work, what doesn't cascade, and how to handle rollback. The mention of the reason field's storage and customer_id fallback (already in schema) ensures an agent knows all necessary context to invoke correctly.

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?

Schema description coverage is 100%, so baseline is 3. The description adds value beyond the schema by clarifying that the 'reason' field is stored in the journal and action log, and that the 'status' field is the only status-setting mechanism (no separate update_status call). It also reinforces the partial-update semantics. This exceeds baseline but does not fully rewrite parameter meanings, so a 4 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 clearly states 'Updates one or more settings on an existing ad group' with a specific verb and resource. It further specifies 'Partial update — only provided fields are changed', which precisely defines its scope. It differentiates from cascading tools like google_ads_ads_update, making its 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 explains when to use this tool (for updating ad group settings) and when not to, stating 'Does not cascade to ads or keywords under this ad group; use google_ads_ads_update / update_status and google_ads.keywords.* for those.' It also clarifies that for status-only changes, this tool is equivalent to setting the status field alone, preventing confusion with a non-existent separate call.

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