Skip to main content
Glama
logly

mureo

by logly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

google_ads_campaigns_update_status

Update a Google Ads campaign's delivery status to ENABLED, PAUSED, or REMOVED. Lightweight status-only write for pausing or resuming campaigns, returning the campaign ID and new status.

Instructions

Sets the delivery status of a single campaign to ENABLED, PAUSED, or REMOVED. Lightweight — writes only the status field. Returns the campaign ID and new status. Reversible via rollback_apply for ENABLED ↔ PAUSED; REMOVED is a soft delete that can be reversed by setting status back to PAUSED within 30 days. Use this for pause/resume; use google_ads_campaigns_update to change name, bidding, or other settings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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 campaign stops serving and is excluded from most default listings but remains queryable by ID.
campaign_idYesCampaign 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.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 behavioral burden and succeeds: it states the tool is lightweight, writes only the status field, returns the campaign ID and new status, and clarifies that REMOVED is a soft delete with a 30-day reversal window. This gives the agent accurate expectations about side effects and recovery.

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?

Every sentence earns its place: behavior, scope, return value, reversibility, and sibling routing are all packed into a compact paragraph without redundancy. The most actionable information (what the tool does) is front-loaded.

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 simple status-update tool with 4 parameters and no output schema, the description covers behavior, side effects, reversibility, and alternatives. The only minor gap is absence of an explicit error/edge-case statement, but the provided context is sufficient for an agent to invoke it 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 coverage is 100%, so the schema already documents all parameters well. The description adds value by clarifying the meaning of REMOVED as a soft delete and by explaining how the optional customer_id falls back to configured credentials, which complements rather than repeats the schema.

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 ('Sets'), a precise resource ('delivery status of a single campaign'), and enumerates the exact allowed values (ENABLED, PAUSED, REMOVED). It also disambiguates from google_ads_campaigns_update by stating this tool only writes the status field, making the purpose unmistakable.

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 tells the agent when to use this tool ('Use this for pause/resume') and when not to ('use google_ads_campaigns_update to change name, bidding, or other settings'). It also explains reversibility paths for each state, so the agent can plan multi-step operations without ambiguity.

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