Skip to main content
Glama

Visibility Genies

Read Google Ads breakdowns

get_google_ads_breakdowns
Read-only

Where and when the connected Google Ads account's ads ran in a period, from what the daily pull stored: the account's impressions, clicks, cost and conversions by device (MOBILE, DESKTOP, TABLET, CONNECTED_TV), by network (SEARCH, SEARCH_PARTNERS, CONTENT, YOUTUBE_SEARCH, YOUTUBE_WATCH, MIXED) and by day of the week, most spend first. Device and network numbers are stored from numbersStartOn; the day of the week covers every stored campaign day. Money is in the account's currency (currencyCode). Read-only; uses no credits.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "projectId": "<projectId>"
    },
    "name": "get_google_ads_breakdowns"
  }
}

Input Schema

NameRequiredDescriptionDefault
rangeNoA named period ending on the last stored day (default last_3_months). Ignored when startDate and endDate are given.
endDateNoLast day (YYYY-MM-DD). Use with startDate; at most 730 days.
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.
startDateNoFirst day (YYYY-MM-DD, the Ads account's time zone).

Output Schema

NameRequiredDescriptionDefault
okYes
metaNo
reasonNo
devicesNo
endDateNo
hasMoreNo
messageNo
failedAtNo
networksNo
rowCountNo
weekdaysNo
startDateNo
connectUrlNo
storedFromNo
accountNameNo
currencyCodeNo
storedThroughNo
numbersStartOnNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds real context beyond that: it identifies the data provenance ('from what the daily pull stored'), states 'uses no credits,' and discloses coverage caveats (device and network figures start at numbersStartOn, while day of week covers every stored campaign day) plus the currency basis and 'most spend first' ordering.

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

Conciseness3/5

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

The purpose is front-loaded in the opening clause, which is good, but the single run-on sentence is dense and spends significant space enumerating device and network values that the schema already constrains. Those parenthetical lists duplicate structured data rather than adding value.

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?

An output schema exists, so return shape need not be described. Given that, the description covers the essential context for a read-only analytics tool: what dimensions are broken out, the data source, coverage limits, currency, and sort order. Only explicit sibling routing is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3; the description nonetheless adds meaning by explaining that device and network aggregates are limited to data stored from numbersStartOn, while day-of-week aggregates span all stored campaign days. That distinction materially affects how an agent should interpret startDate/endDate and range selections, going beyond the schema's field-level notes.

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 states a specific verb-and-resource combination: it returns Google Ads performance (impressions, clicks, cost, conversions) broken down by device, network, and day of week. That is clearly distinguishable from siblings such as get_google_ads_campaigns or get_google_ads_search_terms, which report different cuts of the same account.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage, since it explains that the data comes 'from what the daily pull stored' and that a period is involved, but it never says when to pick this tool over the campaign-level or search-term tools. There are no explicit exclusions or alternative-routing guidance, so the agent has to infer that this tool is for device/network/day-of-week cuts.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources