Delmain GA4 MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DELMAIN_GA4_CLIENT_ID | Yes | OAuth client ID from Google Cloud | |
| DELMAIN_GA4_CLIENT_SECRET | Yes | OAuth client secret from Google Cloud |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_propertiesA | List every GA4 account and property the authenticated user can read. Use this first to discover property IDs. Returns account name, property name, and the numeric property_id needed by every other tool. |
| get_propertyA | Get metadata for one GA4 property: display name, time zone, currency. property_id: numeric GA4 property ID (e.g. "463688888"). If omitted, uses DELMAIN_GA4_PROPERTY_ID from the environment when set. |
| run_reportA | Run a GA4 report with arbitrary dimensions and metrics. property_id: numeric GA4 property ID. Call list_properties() to find it. dimensions: GA4 dimension API names, e.g. ["sessionSource", "sessionMedium"], ["landingPage"], ["date"], ["country"], ["deviceCategory"], ["eventName"]. Pass [] for a single totals row. metrics: GA4 metric API names, e.g. ["sessions", "totalUsers", "newUsers", "screenPageViews", "bounceRate", "averageSessionDuration", "conversions", "eventCount"]. Defaults to ["sessions"]. start_date / end_date: either "YYYY-MM-DD" or relative like "7daysAgo", "28daysAgo", "today", "yesterday". limit: max rows (default 50). order_by_metric: metric name to sort by (e.g. "sessions"). Empty = API default. order_desc: sort descending when order_by_metric is set. |
| run_realtime_reportA | Run a GA4 realtime report (active users in roughly the last 30 minutes). property_id: numeric GA4 property ID. dimensions: e.g. ["unifiedScreenName"], ["country"], ["deviceCategory"]. metrics: e.g. ["activeUsers"], ["screenPageViews"]. Defaults to ["activeUsers"]. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clear, distinct purpose: get_property fetches metadata for one property, list_properties discovers all accessible properties, run_realtime_report provides real-time data, and run_report handles historical reports. There is no overlap, and agents can easily distinguish which tool to use.
All tool names follow a consistent verb_noun pattern in snake_case (get_property, list_properties, run_realtime_report, run_report), making naming predictable and easy to understand.
With only 4 tools, the set is on the smaller side for a GA4 server. While the tools cover basic property retrieval and reporting, additional tools for dimension/metric discovery, account management, or specialized reports (e.g., funnel, cohort) could be expected. The count is acceptable but leaves room for expansion.
The tool surface covers essential read-only operations: property discovery, metadata, real-time data, and historical reports. However, it lacks tools for listing dimension/metric definitions, managing properties, or running more advanced analysis types like funnels or cohorts. Users may need to rely on external knowledge for dimension/metric names.