Skip to main content
Glama
Sign In
ga4-mcp

ga4-mcp

by onionst
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

ga4_metadata

List compatible GA4 dimensions and metrics for a property, with optional text filtering to narrow results.

Instructions

List compatible GA4 dimensions and metrics, optionally filtered by text.

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": {
      "property_id": "<property_id>"
    },
    "name": "ga4_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
searchNo
property_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only says 'List compatible GA4 dimensions and metrics.' It does not clarify what 'compatible' means (e.g., with the GA4 API, the property, or the reporting tool), nor does it mention auth requirements, rate limits, or the return shape. A read operation is implied but not explicit.

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?

The description is a single efficient sentence with no filler. The main action and optional filter are front-loaded. It earns high marks for brevity, though it sacrifices some explanatory depth.

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

Completeness3/5

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

The tool is simple (2 params, 1 required, output schema present), so a short description is partly forgivable. However, with 0% schema coverage and no annotations, the ambiguity of 'compatible' and the unexplained required property_id leave meaningful gaps in context for an agent deciding whether and how to call this tool.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. The phrase 'filtered by text' maps to the 'search' parameter, but the required 'property_id' parameter is not mentioned or explained. An agent must infer that property_id identifies the GA4 property for which metadata is being listed.

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

Purpose4/5

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

The description states a specific verb ('List') and resource ('compatible GA4 dimensions and metrics'), with an optional filter. It is clear and distinct from siblings like ga4_run_report (runs reports) and ga4_list_properties (lists properties), though it does not explicitly name them.

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 this is for discovering available dimensions/metrics, likely before constructing a report. However, it provides no explicit when-to-use guidance, exclusions, or mention of alternatives such as ga4_run_report, leaving the usage context to inference.

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

Deploy Server

Other Tools