Skip to main content
Glama
logly

mureo

by logly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

google_ads_campaigns_update

Update specific settings on a Google Ads campaign while preserving all unmentioned fields. Returns the updated campaign record for confirmation.

Instructions

Updates one or more settings on an existing campaign. Partial update — only fields provided are changed; omitted fields are preserved. Returns the updated campaign record. Mutating — not automatically reversible; record before-state with mureo_state_action_log_append if you may need to roll back. For status-only changes (ENABLED / PAUSED / REMOVED) prefer google_ads_campaigns_update_status, which is a lighter-weight call and maps cleanly to pause/resume workflows.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoNew campaign 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.
campaign_idYesCampaign 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.
bidding_strategyNoNew bidding strategy. Switching strategies can reset learning periods — confirm with the operator before changing on an ENABLED campaign.

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 burden of behavioral disclosure. It clearly states the operation is mutating, not automatically reversible, advises recording before-state for rollback, and notes that omitted fields are preserved. It also says the updated campaign record is returned, which is valuable since there is no output schema.

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, front-loaded with the core purpose and partial-update behavior, and every sentence earns its place. The mutation warning, rollback instruction, and sibling routing are all packed efficiently without redundancy.

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?

The description covers what the tool does, what partial update means, what it returns, the mutation risk, and when to use a different tool. Given the schema already documents required and optional parameters, no critical operational context 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 the schema already documents each parameter meaningfully. The tool description itself adds little param-level detail, but that is acceptable because the schema carries the heavy lifting. 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 states a specific verb ('Updates'), a clear resource ('existing campaign'), and the precise semantics of a partial update. It also distinguishes itself from the lighter-weight google_ads_campaigns_update_status sibling, so an agent can immediately tell which tool handles which scenario.

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 says to prefer google_ads_campaigns_update_status for status-only changes, gives the exact reason (lighter-weight, maps to pause/resume workflows), and explains when the general update tool is appropriate. This is model usage guidance with a clear alternative.

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