Skip to main content
Glama
logly

mureo

by logly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

google_ads_ads_update_status

Pause, resume, or remove a single Google Ads ad by updating its delivery status. Use this tool to change ad status without affecting creative copy or learning signals.

Instructions

Sets the delivery status of a single ad to ENABLED, PAUSED, or REMOVED. Lightweight — writes only the status field and does not reset learning signals. Returns the ad ID and new status. Reversible via rollback_apply. Use this for pause/resume; use google_ads_ads_update to change the creative copy itself.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ad_idYesAd ID.
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.
statusYesTarget status. REMOVED is a soft delete — the ad stops serving but remains queryable by ID.
ad_group_idYesParent ad group ID.
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?

No annotations are provided, so the description carries the full burden — and it delivers: 'writes only the status field and does not reset learning signals' scopes the side effects, 'Returns the ad ID and new status' defines the return contract, and 'Reversible via rollback_apply' discloses undo behavior. The schema adds that REMOVED is a soft delete that remains queryable. This is strong behavioral disclosure for a mutation tool with zero annotation coverage.

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 with zero waste; the core action is front-loaded and every subsequent sentence earns its place: behavioral consequences, return value, rollback path, and sibling differentiation. Despite carrying substantial guidance, the description remains compact and scannable.

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 write tool with no annotations and no output schema, the description compensates fully: it states the return value, the narrow mutation scope, the preservation of learning signals, and reversibility. Combined with a 100%-covered schema (5/5 parameters), an agent has everything needed to select and invoke the tool 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 every parameter (ad_id, ad_group_id, status, reason, customer_id) is already documented with types, constraints, enums, and credential fallback behavior. The description adds operational context — the pause/resume use case and learning-signal preservation — but provides no parameter-specific syntax beyond what the schema already states. Baseline 3 applies.

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 and resource: 'Sets the delivery status of a single ad' with the three permissible values (ENABLED, PAUSED, REMOVED) enumerated. It explicitly differentiates from sibling google_ads_ads_update by noting that tool changes 'the creative copy itself,' so an agent can select correctly without opening either 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 routes usage with a when/when-not pairing: 'Use this for pause/resume; use google_ads_ads_update to change the creative copy itself.' It also names the recovery path via rollback_apply, giving the agent a clear alternative for undoing the change. This is explicit usage guidance, not merely implied.

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