Skip to main content
Glama
logly

mureo

by logly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

google_ads_budget_update

Update an existing Google Ads campaign budget by setting a new daily or total amount. Check shared-budget reference count first, and note CUSTOM_PERIOD is required for total amounts.

Instructions

Sets the daily and/or total amount on an existing campaign budget. Mutating — not automatically reversible; record before-state with mureo_state_action_log_append if you may need to roll back. Returns the updated budget. If the budget is shared across multiple campaigns, the change affects all of them — call google_ads_budget_get first to check reference_count. The amount parameter is in the account's currency unit (JPY / USD / etc.), not micros. The budget's period (DAILY / CUSTOM_PERIOD) is immutable in the Google Ads API — total amounts only apply to budgets created with period='CUSTOM_PERIOD'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
amountNoNew daily budget in the account's currency (JPY / USD / etc.). Not micros — e.g. pass 5000 for ¥5,000 / day. Mutually exclusive with amount_micros.
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.
budget_idYesBudget ID as returned by google_ads_budget_get.
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.
total_amountNoNew total (lifetime) amount in the account's currency. Only applies to CUSTOM_PERIOD budgets — the API rejects it on DAILY budgets. Mutually exclusive with total_amount_micros.
amount_microsNoNew daily budget in micros (currency unit × 1,000,000). Use this for an exact value with no float rounding (e.g. when restoring a prior amount on rollback). Mutually exclusive with amount.
total_amount_microsNoNew total (lifetime) amount in micros. Only applies to CUSTOM_PERIOD budgets — the API rejects it on DAILY budgets. Use for an exact value with no float rounding. Mutually exclusive with total_amount.

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. Changed3 schema fields changedv0.10.19
    • changedInput schema / anyOf
      Previous value: -[
-  {
-    "required": [
-      "amount"
-    ]
-  },
-  {
-    "required": [
-      "amount_micros"
-    ]
-  }
-]New value: +[
+  {
+    "required": [
+      "amount"
+    ]
+  },
+  {
+    "required": [
+      "amount_micros"
+    ]
+  },
+  {
+    "required": [
+      "total_amount"
+    ]
+  },
+  {
+    "required": [
+      "total_amount_micros"
+    ]
+  }
+]
    • addedInput schema / properties / total_amount
      Added value: +{
+  "description": "New total (lifetime) amount in the account's currency. Only applies to CUSTOM_PERIOD budgets — the API rejects it on DAILY budgets. Mutually exclusive with total_amount_micros.",
+  "minimum": 1,
+  "type": "number"
+}
    • addedInput schema / properties / total_amount_micros
      Added value: +{
+  "description": "New total (lifetime) amount in micros. Only applies to CUSTOM_PERIOD budgets — the API rejects it on DAILY budgets. Use for an exact value with no float rounding. Mutually exclusive with total_amount.",
+  "minimum": 1,
+  "type": "integer"
+}
  4. Addedv0.10.11
  5. Removedv0.10.9
  6. Changed4 schema fields changedv0.10.7
    • addedInput schema / anyOf
      Added value: +[
+  {
+    "required": [
+      "amount"
+    ]
+  },
+  {
+    "required": [
+      "amount_micros"
+    ]
+  }
+]
    • changedInput schema / properties / amount / description
      Previous value: -"New daily budget in the account's currency (JPY / USD / etc.). Not micros — e.g. pass 5000 for ¥5,000 / day."New value: +"New daily budget in the account's currency (JPY / USD / etc.). Not micros — e.g. pass 5000 for ¥5,000 / day. Mutually exclusive with amount_micros."
    • addedInput schema / properties / amount_micros
      Added value: +{
+  "description": "New daily budget in micros (currency unit × 1,000,000). Use this for an exact value with no float rounding (e.g. when restoring a prior amount on rollback). Mutually exclusive with amount.",
+  "minimum": 1,
+  "type": "integer"
+}
    • changedInput schema / required
      Previous value: -[
-  "budget_id",
-  "amount"
-]New value: +[
+  "budget_id"
+]
  7. Addedv0.9.12
  8. Removedv0.9.6
  9. Addedv0.9.2
  10. Removedv0.9.1
  11. Addedv1.0.5

TDQS

A4.7/5.0
Behavior5/5

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It fully discloses that the mutation is not automatically reversible, that changes to shared budgets affect all linked campaigns, that the budget period is immutable in the API, and that the tool returns the updated budget. This is unusually transparent for a mutating 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?

The description is dense but every sentence earns its place: the core action, the reversibility warning, the rollback guidance, the return value, the shared-budget side effect, and the API restriction on period/total amounts. It is front-loaded with the most important facts and contains no filler or repetition.

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?

Given the tool's complexity — 7 parameters with four mutually exclusive amount fields, a mutating side effect, shared-budget implications, and an API-level restriction — the description covers all critical operational concerns. It also states the return value, which matters because no output schema is provided.

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 each parameter already has a clear semantic description including mutual-exclusion constraints. The tool description reinforces the currency-vs-micros distinction and the CUSTOM_PERIOD restriction, but adds little new parameter-level meaning beyond what the schema already provides; the baseline of 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 opens with 'Sets the daily and/or total amount on an existing campaign budget,' which names a specific verb, a specific resource, and the exact scope of the operation. It distinguishes itself from related tools like google_ads_budget_create and google_ads_budget_reallocation by targeting an existing budget and directly setting amounts rather than creating or reallocating.

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 gives explicit usage guidance: it flags the operation as mutating and non-reversible, advises recording the before-state with mureo_state_action_log_append when rollback may be needed, and instructs the agent to call google_ads_budget_get first when shared budgets are possible. It also states when total_amount fields are valid versus invalid, which prevents incorrect calls.

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