Skip to main content
Glama
logly

mureo

by logly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

google_ads_negative_keywords_add_to_ad_group

Add negative keywords to a specific Google Ads ad group to block unwanted searches from triggering ads there. Use this when exclusions apply only to that ad group, not the whole campaign.

Instructions

Adds one or more ad group-level negative keywords. Scope is narrower than campaign-level negatives — exclusions apply only to the specified ad group. Returns created criterion_ids. Mutating — not automatically reversible; record before-state with mureo_state_action_log_append if you may need to roll back. Prefer this over google_ads_negative_keywords_add when the exclusion is only wrong in one ad group's context.

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.
keywordsYesNegative keywords to add. Each item has `text` and optional `match_type` (BROAD / PHRASE / EXACT).
ad_group_idYesAd group that will receive the negatives. Exclusions do not cascade to sibling ad groups.
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?

With no annotations provided, the description carries the full behavioral disclosure burden. It clearly flags the operation as mutating and not automatically reversible, advises recording before-state with mureo_state_action_log_append for rollback, and states the return value (created criterion_ids). This gives the agent essential safety and expectation-setting context.

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?

Four sentences, each carrying distinct value: action and scope, return value, mutation warning with rollback guidance, and routing to the correct sibling tool. There is no filler or repetition of schema content.

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 mutating tool with no annotations and no output schema, the description covers what the call does, its narrow scope, return value, rollback strategy, and when to prefer it over the sibling. Combined with fully documented parameters, nothing essential is missing for correct invocation.

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 documents all four parameters at 100% coverage, including defaults, format examples, and scope details such as 'Exclusions do not cascade to sibling ad groups.' The description adds nothing parameter-specific beyond the schema, so the baseline score of 3 is appropriate.

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 opens with a specific verb and resource: 'Adds one or more ad group-level negative keywords.' It immediately contrasts this with campaign-level negatives, making the tool's distinct scope clear and differentiating it from google_ads_negative_keywords_add at a glance.

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 names the alternative google_ads_negative_keywords_add and states the condition for choosing this tool: 'when the exclusion is only wrong in one ad group's context.' The scope statement ('exclusions apply only to the specified ad group') further reinforces when this tool is appropriate.

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