Skip to main content
Glama
Google Growth MCP

Google Growth MCP

by kremnyi

ga4_get_metadata

Lists dimensions and metrics available for Google Analytics 4 Data API reports, so you can choose valid fields before querying a property.

Instructions

List dimensions and metrics available to Google Analytics Data API reports for a GA4 property.

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_get_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
property_idYesNumeric GA4 property ID or properties/{id}.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/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 behavioral burden. 'List' implies a read-only operation, but nothing states auth/permission requirements, whether the response is filtered by the property, or what the returned entries look like (API names vs. UI names, categories), which is critical for this tool's purpose.

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?

A single well-formed sentence that front-loads the action and resource with no filler. It is efficient, though it leaves little room for the context that would make it genuinely helpful.

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?

For a one-parameter metadata listing tool with no output schema, the description is minimally adequate but omits what the agent most needs to know: that the returned dimension/metric identifiers are what feed into report requests. Nothing is misleading, but the definition does not fully close the gap left by absent annotations and output schema.

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?

There is a single parameter with 100% schema description coverage ('Numeric GA4 property ID or properties/{id}'), so the schema already does the work. The description only restates 'for a GA4 property' and adds no format or validation detail beyond the schema, matching the baseline of 3.

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 gives a specific verb and resource ('List dimensions and metrics available to Google Analytics Data API reports') scoped to a GA4 property, which is clearly distinct from sibling tools like ga4_run_report or ga4_list_account_summaries. It stops short of explicitly contrasting itself with the report-running siblings, so a 4 rather than a 5.

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?

Mentioning that the dimensions and metrics are those 'available to Google Analytics Data API reports' hints that this is a discovery step before building a report, but the description never says when to call it, whether it should precede ga4_run_report, or any exclusions. Usage is only implied.

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