Skip to main content
Glama
logly

mureo

by logly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

google_ads_conversions_performance

Report Google Ads conversions by conversion action and date, optionally filtered by campaign, including daily details, landing page breakdowns, and cost per conversion for performance analysis.

Instructions

Report Google Ads conversions broken down by conversion_action and date, with optional campaign filter. Returns {period, campaign_id, total_conversions, actions:[{campaign_id, campaign_name, conversion_action_name, conversions, conversions_value, first_date, last_date, cost_per_conversion}] (sorted by conversions desc), daily_details:[{date, campaign_id, campaign_name, conversion_action_name, conversions, conversions_value}], landing_pages:[{date, landing_page_url, campaign_id, campaign_name, conversions, conversions_value, clicks}]}. Only rows with conversions > 0 are included. cost_per_conversion is computed via a separate GAQL because GAQL cannot SELECT cost_per_conversion alongside segments.conversion_action_name; it is null when that cost read fails. landing_pages is null when the landing-page read fails. Read-only. For campaign-level metrics use google_ads_performance_report.

Input Schema

NameRequiredDescriptionDefault
periodNoReporting window. Default 'LAST_30_DAYS'. Use LAST_7_DAYS / LAST_14_DAYS for recent diagnosis; LAST_90_DAYS for baseline. 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_idNoOptional campaign ID as a numeric string to restrict the report. Omit for account-wide aggregation.
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: -"Reporting window. Default 'LAST_30_DAYS'. Use LAST_7_DAYS / LAST_14_DAYS for recent diagnosis; LAST_90_DAYS for baseline. 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: +"Reporting window. Default 'LAST_30_DAYS'. Use LAST_7_DAYS / LAST_14_DAYS for recent diagnosis; LAST_90_DAYS for baseline. 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. Changed3 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: -"Reporting window. Default 'LAST_30_DAYS'. Use LAST_7_DAYS / LAST_14_DAYS for recent diagnosis; LAST_90_DAYS for baseline."New value: +"Reporting window. Default 'LAST_30_DAYS'. Use LAST_7_DAYS / LAST_14_DAYS for recent diagnosis; LAST_90_DAYS for baseline. 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."
    • removedInput schema / properties / period / enum
      Removed value: -[
-  "TODAY",
-  "YESTERDAY",
-  "LAST_7_DAYS",
-  "LAST_14_DAYS",
-  "LAST_30_DAYS",
-  "LAST_90_DAYS",
-  "THIS_MONTH",
-  "LAST_MONTH"
-]
  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. Addedv1.0.5

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and handles it well: it declares 'Read-only', discloses the silent filter 'Only rows with conversions > 0 are included', and documents degraded-failure modes ('cost_per_conversion ... is null when that cost read fails', 'landing_pages is null when the landing-page read fails'). It stops short of permissions/auth requirements or row-limit/rate behavior, so not a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and scope are front-loaded in the first clause, followed by return shape, then caveats, then sibling routing — a sound order. The middle sentence is a dense nested-brace dump, but it substitutes for a missing output schema, so most of that bulk earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description must enumerate return keys, sort order, and null conditions — which it does thoroughly. Remaining gaps are minor: no note on result-size limits, pagination, or what counts as a 'conversion' across the listed actions.

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 coverage is 100%, and the period/campaign_id/customer_id semantics live entirely in the schema descriptions, not the tool description. The description adds the campaign filter's effect on aggregation only implicitly ('optional campaign filter'), so baseline 3 applies.

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?

States a specific verb and resource ('Report Google Ads conversions broken down by conversion_action and date, with optional campaign filter') and explicitly routes the agent away from the sibling used for campaign-level metrics. An agent can distinguish it from google_ads_performance_report and google_ads_conversions_list without opening a 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?

The closing sentence 'For campaign-level metrics use google_ads_performance_report' gives an explicit alternative with the condition that selects it. However, it does not distinguish this report from adjacent read tools like google_ads_conversions_list or google_ads_monitoring_cv_goal, and gives no guidance on when this report is the wrong granularity.

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