Google Analytics 4 by Get MCP Ads

ga4 get ecommerce diagnostics

ga4_get_ecommerce_diagnostics

Read-onlyIdempotent

Diagnose ecommerce tracking coverage for core events, revenue metrics, and item-level reporting across a date range. Identify gaps to improve GA4 data completeness.

Instructions

Read-only ecommerce coverage diagnostics for core ecommerce events, revenue metrics, and item-level reporting over a date range.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Maximum number of returned items or rows. The declared bounds and default apply; use pagination for additional results.
`endDate`	No	End date YYYY-MM-DD or relative (today, yesterday)
`startDate`	No	Start date YYYY-MM-DD or relative (7daysAgo, yesterday)
`datePreset`	No	Named reporting period. Use the custom date range when you need exact start and end dates.	last28days
`propertyId`	Yes	GA4 property ID (numeric, e.g., 123456789)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes	Original tool result: parsed JSON when the text is JSON, otherwise the text or multiple MCP content blocks. Provider fields depend on the selected query.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.1Sep 23, 2026

TDQS

A3.8/5.0

Behavior3/5

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

The description labels the tool 'Read-only', which matches the annotations (readOnlyHint=true, idempotentHint=true, destructiveHint=false), but this adds no new behavioral information beyond the annotations. It provides useful context about the diagnostic scope (events, revenue, item-level reporting) but does not disclose additional behavioral traits such as rate limits or data freshness.

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 description is a single sentence that front-loads the read-only nature and clearly specifies the diagnostic subject and time scope. It contains no filler or redundant phrasing and is highly scannable.

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?

Given the presence of an output schema and rich annotations, the description sufficiently conveys the purpose and scope for an agent to decide to invoke it. It could be more explicit about what 'coverage diagnostics' means in terms of output, but the output schema likely covers return structure. Minor gap: no guidance on how this relates to other reporting tools.

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%, so the input schema fully documents all five parameters including defaults and date formats. The description adds only the general notion of 'over a date range', which is already captured by startDate, endDate, and datePreset. No additional parameter-level meaning is provided.

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 clearly identifies the tool as 'Read-only ecommerce coverage diagnostics' and specifies the covered areas: core ecommerce events, revenue metrics, and item-level reporting over a date range. This distinguishes it from sibling diagnostics like audience, BigQuery, or server-side tagging diagnostics.

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 for ecommerce coverage diagnostics but provides no explicit guidance on when to prefer this over ga4_run_report, ga4_run_pivot_report, or other diagnostics tools. No alternatives or exclusion conditions are mentioned, so the agent must infer from the name and description.

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