Skip to main content
Glama
logly

mureo

by logly
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

google_ads_network_performance_report

Analyze Google Ads performance by network (Google Search vs Search Partners) to decide whether to toggle Search Partners. Returns impressions, clicks, cost, conversions, CTR, and CPC per campaign and network.

Instructions

Report Google Ads performance split by ad network — Google Search vs. Search Partners. Returns one row per (campaign, network) shaped as {campaign_id, campaign_name, network_type ('SEARCH'|'SEARCH_PARTNERS'), network_label ('Google Search'|'Search Partners'), impressions, clicks, cost, conversions, ctr (percent), average_cpc, cost_per_conversion}. Display, YouTube, and Discover rows are filtered out. ctr, average_cpc, and cost_per_conversion are rounded to whole-unit currency. Read-only. Use this to decide whether to toggle Search Partners. For overall campaign totals use google_ads_performance_report; for per-ad breakdowns use google_ads_ad_performance_report.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
periodNoReporting window for the metrics. Default 'LAST_30_DAYS'. Use a shorter window (LAST_7_DAYS / LAST_14_DAYS) when diagnosing recent changes; use LAST_90_DAYS for trend baselines. 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.
campaign_idNoOptional campaign ID as a numeric string (e.g. '23743184133') to restrict the report to a single campaign. Omit to aggregate across every campaign in the account.
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. Dates show when Glama detected each change.

  1. 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 for the metrics. Default 'LAST_30_DAYS'. Use a shorter window (LAST_7_DAYS / LAST_14_DAYS) when diagnosing recent changes; use LAST_90_DAYS for trend baselines."New value: +"Reporting window for the metrics. Default 'LAST_30_DAYS'. Use a shorter window (LAST_7_DAYS / LAST_14_DAYS) when diagnosing recent changes; use LAST_90_DAYS for trend baselines. 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"
-]
  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, the description carries the full disclosure burden and meets it: it declares the operation read-only, describes the exact row shape, lists which networks are filtered out, and specifies rounding behavior. This gives an agent accurate expectations beyond the bare tool name.

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 purpose is front-loaded, each sentence contributes a distinct fact (scope, shape, filters, rounding, use case, alternatives), and there is no filler. The length is justified by the absence of an output schema, which makes the inline result-shape specification valuable.

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?

Given no output schema, the description fills the gap by specifying the returned fields and their allowed values, and also supplies filtering, rounding, and routing context. The remaining details (period semantics, optional IDs, credential fallback) are already thoroughly documented in the input schema, so nothing an agent needs to invoke it correctly 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?

The input schema has 100% description coverage, including a detailed explanation of the period values and the customer_id fallback, so the description does not need to restate parameter meaning. It adds no extra parameter-level detail, which matches the baseline of 3 for high schema coverage.

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-plus-resource statement: it 'report[s] Google Ads performance split by ad network — Google Search vs. Search Partners.' It also names the sibling alternatives (google_ads_performance_report and google_ads_ad_performance_report), so an agent can tell immediately which report is which.

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 gives an explicit decision context: 'Use this to decide whether to toggle Search Partners.' It also gives clear exclusion routing: 'For overall campaign totals use google_ads_performance_report; for per-ad breakdowns use google_ads_ad_performance_report,' and states that Display, YouTube, and Discover rows are filtered out.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/logly/mureo'

If you have feedback or need assistance with the MCP directory API, please join our Discord server