google_ads_get_performance_report

Description

Segmented and multi-level performance reporting. FIRST, CHECK THE REQUEST: for a plain account-level overview with no segments and no level breakdown — a quick performance summary, "how is this account doing", or account totals over a date range — use google_ads_get_account_summary instead; it returns those totals pre-aggregated in a single call. Use this tool when a level (CAMPAIGN, AD_GROUP) or a segment (device, date, network type) is actually needed. Comprehensive funnel metrics with per-conversion-action breakdowns. Supports segments for device breakdown (DESKTOP, MOBILE, TABLET), daily trends, and network type analysis. Preferred over google_ads_get_insights for standard analysis. Runs parallel queries for top-level funnel and conversion action breakdown. Supported levels automatically include the Demand Gen Platform Comparable conversion family (platform_comparable_conversions, cost/value/rate variants); row-level reports return null for non-Demand Gen rows. Search impression share is included at CAMPAIGN and AD_GROUP levels (budget-lost variants campaign-level only). Set include_new_vs_returning to add a conversions breakdown by new vs returning customer (segments.new_versus_returning_customers; new customers = NEW + NEW_AND_HIGH_LTV buckets summed) for cost-per-new-customer reporting on customer-acquisition-goal campaigns. Use google_ads_get_insights for custom metric selection. For geographic data, use google_ads_get_geo_performance instead. Paginated: data holds up to limit rows (default 15, or 10 with include_all_conversions or include_new_vs_returning; max 1000) in a stable order (entity ids, then segment values), count is the total across all pages, and the conversion breakdowns cover only the rows on the current page; a breakdown key shared by rows on several pages (at AD level, an ad running in two ad groups) is listed once, on the first page that holds it. When nextCursor is present, call again with the same parameters and cursor set to nextCursor until it is absent. To get every row, follow the cursor rather than raising limit: a larger page can exceed MCP client response limits.

Usage

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "google_ads_get_performance_report",
    "arguments": {
      "customer_id": "1234567890",
      "date_preset": "LAST_30_DAYS",
      "reason": "Monthly performance review"
    }
  }
}

hopkin google performance-report get

{
  "mcpServers": {
    "google-ads": {
      "url": "https://google.mcp.hopkin.ai",
      "transport": "sse"
    }
  }
}

Parameters

Examples

{
  "customer_id": "1234567890",
  "date_preset": "LAST_30_DAYS",
  "reason": "Monthly performance review"
}

{
  "customer_id": "1234567890",
  "date_preset": "LAST_7_DAYS",
  "segments": [
    "date"
  ],
  "reason": "Daily performance trend"
}

{
  "customer_id": "1234567890",
  "date_preset": "LAST_30_DAYS",
  "level": "ACCOUNT",
  "reason": "Account-level overview"
}

{
  "customer_id": "1234567890",
  "date_preset": "LAST_30_DAYS",
  "segments": [
    "device"
  ],
  "reason": "Device analysis"
}

{
  "customer_id": "1234567890",
  "date_preset": "LAST_30_DAYS",
  "include_new_vs_returning": true,
  "reason": "New vs returning customer acquisition analysis"
}

Related Tools