Skip to main content
Glama
logly

mureo

by logly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

google_ads_keywords_cross_adgroup_duplicates

Finds duplicate keywords across ad groups in a campaign and returns per-copy spend, conversions, and quality score with a consolidation recommendation to keep or pause copies.

Instructions

Finds the same text+match_type keyword appearing across multiple ad groups in a campaign. Returns groups of duplicate criteria with per-ad-group spend, conversions, and quality score, plus a consolidation recommendation (which copy to keep, which to pause/remove). Read-only. Duplicates compete in the auction and hurt aggregate quality score — run this before a keyword restructuring sprint.

Input Schema

NameRequiredDescriptionDefault
periodNoAnalysis window used to compute per-copy spend and conversions. Default 'LAST_30_DAYS'. Also accepts an explicit range — "YYYY-MM-DD..YYYY-MM-DD" (the spelling Meta Ads takes too) or, in GAQL spelling, "BETWEEN 'YYYY-MM-DD' AND 'YYYY-MM-DD'" — both endpoints inclusive, in the account's time zone, for a window no trailing constant can reach (e.g. a single past calendar month). One asymmetry to know about: every constant except LAST_90_DAYS is resolved by Google Ads in the account's reporting time zone, whereas LAST_90_DAYS has no API constant and is expanded by mureo into the 90 days ending yesterday **on the server's date**, so its edges can differ by a day when the server and the account are in different zones. Pass an explicit range when the exact boundary matters.
campaign_idYesCampaign to scan for duplicates.
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. Changed2 schema fields changedv0.33.0
    • changedInput schema / properties / period / anyOf
      Previous value: -[
-  {
-    "enum": [
-      "TODAY",
-      "YESTERDAY",
-      "THIS_WEEK_SUN_TODAY",
-      "THIS_WEEK_MON_TODAY",
-      "LAST_BUSINESS_WEEK",
-      "LAST_WEEK_SUN_SAT",
-      "LAST_WEEK_MON_SUN",
-      "LAST_7_DAYS",
-      "LAST_14_DAYS",
-      "LAST_30_DAYS",
-      "LAST_90_DAYS",
-      "THIS_MONTH",
-      "LAST_MONTH"
-    ],
-    "type": "string"
-  },
-  {
-    "pattern": "\\ABETWEEN '([0-9]{4}-[0-9]{2}-[0-9]{2})' AND '([0-9]{4}-[0-9]{2}-[0-9]{2})'\\Z",
-    "type": "string"
-  }
-]New value: +[
+  {
+    "enum": [
+      "TODAY",
+      "YESTERDAY",
+      "THIS_WEEK_SUN_TODAY",
+      "THIS_WEEK_MON_TODAY",
+      "LAST_BUSINESS_WEEK",
+      "LAST_WEEK_SUN_SAT",
+      "LAST_WEEK_MON_SUN",
+      "LAST_7_DAYS",
+      "LAST_14_DAYS",
+      "LAST_30_DAYS",
+      "LAST_90_DAYS",
+      "THIS_MONTH",
+      "LAST_MONTH"
+    ],
+    "type": "string"
+  },
+  {
+    "pattern": "\\ABETWEEN '([0-9]{4}-[0-9]{2}-[0-9]{2})' AND '([0-9]{4}-[0-9]{2}-[0-9]{2})'\\Z",
+    "type": "string"
+  },
+  {
+    "pattern": "\\A([0-9]{4}-[0-9]{2}-[0-9]{2})\\.\\.([0-9]{4}-[0-9]{2}-[0-9]{2})\\Z",
+    "type": "string"
+  }
+]
    • changedInput schema / properties / period / description
      Previous value: -"Analysis window used to compute per-copy spend and conversions. Default 'LAST_30_DAYS'. Also accepts an explicit range in GAQL spelling — \"BETWEEN 'YYYY-MM-DD' AND 'YYYY-MM-DD'\", both endpoints inclusive, in the account's time zone — for a window no trailing constant can reach (e.g. a single past calendar month). One asymmetry to know about: every constant except LAST_90_DAYS is resolved by Google Ads in the account's reporting time zone, whereas LAST_90_DAYS has no API constant and is expanded by mureo into the 90 days ending yesterday **on the server's date**, so its edges can differ by a day when the server and the account are in different zones. Pass an explicit range when the exact boundary matters."New value: +"Analysis window used to compute per-copy spend and conversions. Default 'LAST_30_DAYS'. Also accepts an explicit range — \"YYYY-MM-DD..YYYY-MM-DD\" (the spelling Meta Ads takes too) or, in GAQL spelling, \"BETWEEN 'YYYY-MM-DD' AND 'YYYY-MM-DD'\" — both endpoints inclusive, in the account's time zone, for a window no trailing constant can reach (e.g. a single past calendar month). One asymmetry to know about: every constant except LAST_90_DAYS is resolved by Google Ads in the account's reporting time zone, whereas LAST_90_DAYS has no API constant and is expanded by mureo into the 90 days ending yesterday **on the server's date**, so its edges can differ by a day when the server and the account are in different zones. Pass an explicit range when the exact boundary matters."
  2. Changed2 schema fields changedv0.17.1
    • addedInput schema / properties / period / anyOf
      Added value: +[
+  {
+    "enum": [
+      "TODAY",
+      "YESTERDAY",
+      "THIS_WEEK_SUN_TODAY",
+      "THIS_WEEK_MON_TODAY",
+      "LAST_BUSINESS_WEEK",
+      "LAST_WEEK_SUN_SAT",
+      "LAST_WEEK_MON_SUN",
+      "LAST_7_DAYS",
+      "LAST_14_DAYS",
+      "LAST_30_DAYS",
+      "LAST_90_DAYS",
+      "THIS_MONTH",
+      "LAST_MONTH"
+    ],
+    "type": "string"
+  },
+  {
+    "pattern": "\\ABETWEEN '([0-9]{4}-[0-9]{2}-[0-9]{2})' AND '([0-9]{4}-[0-9]{2}-[0-9]{2})'\\Z",
+    "type": "string"
+  }
+]
    • changedInput schema / properties / period / description
      Previous value: -"Analysis window used to compute per-copy spend and conversions. Accepts 'LAST_7_DAYS', 'LAST_14_DAYS', 'LAST_30_DAYS' (default), or 'YYYY-MM-DD..YYYY-MM-DD'."New value: +"Analysis window used to compute per-copy spend and conversions. Default 'LAST_30_DAYS'. Also accepts an explicit range in GAQL spelling — \"BETWEEN 'YYYY-MM-DD' AND 'YYYY-MM-DD'\", both endpoints inclusive, in the account's time zone — for a window no trailing constant can reach (e.g. a single past calendar month). One asymmetry to know about: every constant except LAST_90_DAYS is resolved by Google Ads in the account's reporting time zone, whereas LAST_90_DAYS has no API constant and is expanded by mureo into the 90 days ending yesterday **on the server's date**, so its edges can differ by a day when the server and the account are in different zones. Pass an explicit range when the exact boundary matters."
  3. Changed1 schema field changedv0.10.37
    • addedInput schema / additionalProperties
      Added value: +false
  4. Addedv0.10.11
  5. Removedv0.10.9
  6. Addedv0.9.12
  7. Removedv0.9.6
  8. Addedv0.9.2
  9. Removedv0.9.1
  10. Addedv0.2.0
  11. Removedv0.3.1
  12. Addedv0.3.2
  13. Removedv1.0.6
  14. Addedv1.0.5

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it declares 'Read-only' explicitly and describes the return payload shape (duplicate groups with per-ad-group spend, conversions, quality score, plus a keep/pause/remove recommendation). It omits any statement about permissions, call cost/rate limits, or result volume for large campaigns.

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 short sentences, front-loaded with what it finds, then what it returns, then safety, then the trigger. No redundancy and each sentence adds a distinct fact.

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?

Despite no output schema and no annotations, an agent knows what the tool returns, that it is safe to call, and when it is worth calling. With only three parameters, all fully documented in the schema, nothing material 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% and the schema itself is unusually rich (period constants, explicit-range spellings, timezone asymmetry, customer_id fallback). The description adds nothing about parameters, so baseline 3 applies — the schema is doing all the work.

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?

Names a specific verb and resource with a precise scope: 'the same text+match_type keyword appearing across multiple ad groups in a campaign.' This narrow framing makes it self-distinguishing from the neighbouring list/audit/diagnose keyword tools without needing to name them.

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?

Gives a clear triggering context — 'run this before a keyword restructuring sprint' — and explains why (duplicates compete in the auction, hurt quality score). It does not name alternatives (keywords_audit, keywords_diagnose) or state when-not to use it, so it stops short of full routing guidance.

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