Skip to main content
Glama
logly

mureo

by logly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

google_ads_negative_keywords_remove

Remove a campaign-level negative keyword using campaign and criterion IDs. The exclusion is lifted immediately, so save the prior state if rollback may be needed.

Instructions

Removes a single campaign-level negative keyword. Returns the removed criterion_id. Destructive — the exclusion is lifted immediately on the next serving cycle, which can increase unwanted traffic. Not automatically reversible — record before-state with mureo_state_action_log_append if you may need to roll back. For ad group-level negatives there is currently no explicit remove tool — use the Google Ads UI or raise an issue if needed.

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.
campaign_idYesCampaign ID the negative belongs to.
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_idYesNegative-keyword criterion ID as returned by google_ads_negative_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.5/5.0
Behavior5/5

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

With no annotations present, the description carries full behavioral burden and does so thoroughly: it labels the operation destructive, notes the exclusion is lifted on the next serving cycle, warns about increased unwanted traffic, and states it is not automatically reversible. It also names the specific rollback aid mureo_state_action_log_append, making the risk actionable.

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: action and return value, destructive consequence, rollback guidance, and the ad group-level alternative. The most important operational facts are front-loaded, and there is no redundant filler.

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 tool with no output schema and no annotations, the description is complete: it covers scope, return value, timing, risk, reversibility, rollback, and the fallback for a related case. The schema covers the remaining parameter details, so nothing an agent needs 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.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema fully documents campaign_id, criterion_id, customer_id, and reason. The description adds no additional parameter meaning beyond noting that a criterion_id is returned by the removal; this keeps it at the baseline for well-covered schemas.

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 and resource: 'Removes a single campaign-level negative keyword.' It also distinguishes itself from ad group-level removal and from the sibling add/remove tools by specifying scope, so an agent can tell it apart without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly directs ad group-level negative removal to the Google Ads UI or an issue, and it gives practical guidance to record before-state for rollback. It does not explicitly contrast with the sibling google_ads_negative_keywords_add tool, but the inverse relationship is clear enough from the description.

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