Skip to main content
Glama
logly

mureo

by logly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

google_ads_budget_update

Sets the daily or total amount on an existing Google Ads campaign budget and returns the updated budget. Check reference_count first, since shared budgets change for all linked campaigns.

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

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.
approvalNoExternal approval this change carries out (recorded and shown, never verified)
expectedNoExpected effects [{metric, direction, target?, horizon_days?, primary?}], exactly one primary:true when several; metric cpa/cpc/cpl/cpm/conversions/cvr/ctr/roas/cost/spend/clicks/impressions; direction up/down/hold.
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.
decision_idNoA proposed decision this change carries out.
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.33.0
    • changedInput schema / properties / expected / description
      Previous value: -"Expected effects [{metric, direction, target?, horizon_days?}]; metric cpa/cpc/cpl/cpm/conversions/cvr/ctr/roas/cost/spend/clicks/impressions; direction up/down/hold."New value: +"Expected effects [{metric, direction, target?, horizon_days?, primary?}], exactly one primary:true when several; metric cpa/cpc/cpl/cpm/conversions/cvr/ctr/roas/cost/spend/clicks/impressions; direction up/down/hold."
  2. Changed1 schema field changedv0.28.0
    • addedInput schema / properties / approval
      Added value: +{
+  "additionalProperties": false,
+  "description": "External approval this change carries out (recorded and shown, never verified)",
+  "properties": {
+    "approved_at": {
+      "maxLength": 64,
+      "type": "string"
+    },
+    "approved_by": {
+      "maxLength": 80,
+      "type": "string"
+    },
+    "reference": {
+      "maxLength": 128,
+      "type": "string"
+    }
+  },
+  "required": [
+    "reference",
+    "approved_by",
+    "approved_at"
+  ],
+  "type": "object"
+}
  3. Changed2 schema fields changedv0.26.0
    • addedInput schema / properties / decision_id
      Added value: +{
+  "description": "A proposed decision this change carries out.",
+  "maxLength": 128,
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / expected
      Added value: +{
+  "description": "Expected effects [{metric, direction, target?, horizon_days?}]; metric cpa/cpc/cpl/cpm/conversions/cvr/ctr/roas/cost/spend/clicks/impressions; direction up/down/hold.",
+  "maxItems": 12,
+  "type": "array"
+}
  4. 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"
+}
  5. Changed1 schema field changedv0.10.37
    • addedInput schema / additionalProperties
      Added value: +false
  6. 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"
+}
  7. Addedv0.10.11
  8. Removedv0.10.9
  9. 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"
+]
  10. Addedv0.9.12
  11. Removedv0.9.6
  12. Addedv0.9.2
  13. Removedv0.9.1
  14. Addedv1.0.5

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does: it declares the operation mutating, not automatically reversible, notes shared-budget blast radius across all attached campaigns, and states the return value ('Returns the updated budget'). Currency-vs-micros and the DAILY/CUSTOM_PERIOD rejection rule are real behavioral constraints an agent would otherwise learn only by failing.

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 the non-reversibility warning, then preconditions, then unit semantics — a sensible order. It is dense but nearly every sentence carries a distinct constraint; the shared-budget and period-immutability notes are the only ones that verge on verbose.

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 10-parameter mutation with a nested approval object and no output schema, the description covers the safety profile, the preconditions, the unit traps, and the return value. Nothing an agent needs in order to call it safely is missing.

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 coverage is 100%, so the baseline is 3; the description still adds cross-parameter meaning by explaining when total_amount is legal (CUSTOM_PERIOD only) and reinforcing currency-unit semantics. It stops short of describing the approval/expected/decision_id journaling parameters, which remain schema-only.

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 (sets) and resource (daily/total amount on an existing campaign budget), and the word 'existing' implicitly separates it from google_ads_budget_create while the reference to google_ads_budget_get separates it from the read path. An agent can route correctly without opening any schema.

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?

Explicitly says to log before-state with mureo_state_action_log_append if rollback may be needed, and to call google_ads_budget_get first when the budget might be shared. It also states the period is immutable, which tells the agent when this tool cannot do what the user asked.

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