AdLoop: Google Ads, Reddit Ads & GA4

Overview Schema Source Related Servers Discussions Admin

Analytics dimensions and metrics

list_ga4_dimensions_and_metrics

Read-only

Find valid GA4 dimension and metric API names, including custom fields, for a property so your reports and queries reference the right fields.

Instructions

List the dimensions and metrics a GA4 property can report on, including custom ones.

Returns the exact API names valid in run_ga4_report for this property: each with its UI name, category, whether it is a custom definition (customEvent:..., customUser:...), and deprecated API names; metrics also carry their type and, for calculated metrics, the expression. Reads the GA4 Data API metadata (properties.getMetadata), which uses no report quota.

Google Analytics Data API: https://developers.google.com/analytics/devguides/reporting/data/v1 and Admin API: https://developers.google.com/analytics/devguides/config/admin/v1

Input Schema

TableJSON Schema

Name	Required	Description	Default
`kind`	No	"all" (default), "dimensions" or "metrics".	all
`search`	No	Case-insensitive text matched against API name, UI name, category, description and deprecated API names (e.g. "channel", "revenue", or the legacy "conversions", which finds keyEvents). Empty returns everything.
`custom_only`	No	True returns only the property's custom dimensions and metrics.
`property_id`	No	GA4 property as "properties/123456789" or the bare numeric ID. If empty, uses the default from config.
`include_descriptions`	No	Include each field's description. Defaults to true when search is set and false otherwise (the full list is long).

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.27.1Oct 14, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations cover readOnly/openWorld/non-destructive, but the description adds substantial behavioral context beyond them: it names the underlying API call (properties.getMetadata) and discloses that it consumes no report quota. It also describes the shape of the return (UI name, category, custom prefix markers, deprecated API names, metric type, calculated expression).

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?

Front-loaded with the core purpose and return details in three efficient sentences. The trailing API documentation URLs add some length but are useful references; the content is well-organized and non-redundant.

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

Completeness5/5

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

Given readOnly annotations and a complete output schema, the description covers what an agent still needs: the underlying call, quota implications, return shape, and the relationship to run_ga4_report. Nothing material is missing for correct invocation.

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%, so all five parameters are already documented in the schema with defaults and behavior. The description adds no parameter-level syntax or format detail beyond what the schema provides, which is the expected baseline.

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?

States a specific verb (List) and resource (GA4 dimensions and metrics), and sharply scopes it to what a GA4 property can report on, including custom definitions. The mention of run_ga4_report ('exact API names valid in run_ga4_report') distinguishes it from that sibling by positioning it as the prerequisite lookup.

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

Usage Guidelines4/5

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

The link to run_ga4_report makes the usage context clear: call this to find valid field names before running a report. However, it never explicitly states 'use before run_ga4_report' nor excludes alternatives like run_gaql, leaving some inference to the agent.

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

Deploy Server