Skip to main content
Glama
logly

mureo

by logly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

google_ads_keywords_remove

Permanently soft-delete a keyword from a Google Ads ad group. Choose this only when you no longer need the keyword; otherwise pause to preserve quality score and learning.

Instructions

Removes (soft-deletes) a single keyword criterion from an ad group. Returns the removed criterion_id. Destructive — not automatically reversible; record before-state with mureo_state_action_log_append if you may need to roll back (and note that re-adding the keyword creates a fresh criterion — the original quality score and learning are lost). For temporary suspension prefer google_ads_keywords_pause, which preserves all signals.

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.
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.
criterion_idYesKeyword criterion ID as returned by google_ads_keywords_list.

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 were provided, so the description carries the full burden. It immediately discloses that the operation is destructive, not automatically reversible, and that re-adding the keyword creates a fresh criterion with lost quality score and learning. It also states the return value, which is especially useful given no output schema exists.

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 compact and front-loaded: it opens with the core operation and return value, then layers the destructive warning, rollback guidance, and sibling alternative. Every sentence adds decision-relevant information, and there is no filler or repetition of the schema.

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 destructive mutation tool with no annotations and no output schema, the description is remarkably complete. It covers the action, return value, irreversibility, data-loss consequences, rollback strategy, and the preferred alternative for temporary changes. The schema fully documents parameters, so an agent has everything needed to invoke it 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?

The input schema has 100% description coverage, so the baseline is 3 because the schema already documents every parameter. The description adds meaningful context about the operation's effect (e.g., fresh criterion on re-add), but does not add new details about individual parameter formats beyond what the schema already provides. The schema's parameter descriptions are sufficient.

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 ('Removes (soft-deletes)'), the exact resource ('a single keyword criterion from an ad group'), and the return value ('Returns the removed criterion_id'). It also distinguishes itself from the closely related google_ads_keywords_pause tool by clarifying the semantic difference between removal and suspension.

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?

It explicitly says when to use this tool for permanent removal, and explicitly names the alternative for temporary suspension: 'For temporary suspension prefer google_ads_keywords_pause, which preserves all signals.' It also provides actionable rollback guidance by recommending mureo_state_action_log_append to record before-state, making the when/why usage unmistakable.

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