GA4 Automation MCP Server

get_conversion_data

Retrieve conversion and event data including e-commerce metrics from a GA4 property within a specified date range.

Instructions

Get conversion and event data including conversion events and e-commerce metrics

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": {
      "propertyId": "<propertyId>",
      "startDate": "<startDate>",
      "endDate": "<endDate>"
    },
    "name": "get_conversion_data"
  }
}

Input Schema

Name	Required	Description
`propertyId`	Yes	GA4 property ID
`startDate`	Yes	Start date in YYYY-MM-DD format
`endDate`	Yes	End date in YYYY-MM-DD format

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 12, 2026

TDQS

C2.6/5.0

Behavior2/5

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

No annotations provided, and description only says 'Get' without disclosing any behavioral traits (e.g., read-only, potential for large data, required permissions, pagination). An agent has no indication of side effects or constraints.

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?

Single sentence, 12 words. No fluff, but sacrifices informativeness for brevity. Could include more details without being wordy.

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

Completeness2/5

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

No output schema, so description should provide hints about return format, metrics available, or pagination. Lacks context for a tool with 3 required params and multiple siblings. Incomplete for accurate agent use.

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% with clear descriptions. The description adds no additional semantic value beyond what the schema provides. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States it gets conversion and event data, but vague on specifics. Does not differentiate from siblings like get_custom_report or query_analytics. A more specific resource (e.g., GA4 conversion report) would improve clarity.

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

Usage Guidelines2/5

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

No guidance on when to use vs alternatives. Agent cannot determine if this is the right tool for conversion data compared to other analytics tools. No mention of prerequisites or context.

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

Deploy Server