Skip to main content
Glama
Google Workspace MCP connector

Google Workspace MCP connector

by animesh-ex

ga_get_metadata

Read-only

Lists available dimensions and metrics for a Google Analytics 4 property, including custom fields, and filters them by an optional search term.

Instructions

List the dimensions and metrics available for a GA4 property (including custom ones). Optional search text filters the list.

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>"
    },
    "name": "ga_get_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
searchNo
propertyIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds one useful scope fact beyond annotations — that custom dimensions/metrics are included — but says nothing about result size, pagination, rate limits, or whether the list can be very large for a property with many custom fields.

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?

Two short sentences, front-loaded with the core action and with the filter behavior placed second as a secondary detail. No filler, though it is perhaps terse enough to underserve the required parameter.

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

Completeness4/5

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

A two-parameter read-only discovery tool with no output schema needs little explanation, and the description covers what the list contains and how search narrows it. The remaining gap — propertyId format and result size — is minor for this complexity level.

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 description coverage is 0%, so the description must compensate. It explains the optional 'search' parameter as a text filter on the list but leaves 'propertyId' undescribed beyond the phrase 'for a GA4 property', giving no hint about expected format (e.g. numeric ID vs. 'properties/123'). Partial compensation only.

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?

A specific verb ('List') plus resource ('dimensions and metrics') and scope ('available for a GA4 property, including custom ones'). An agent can distinguish this metadata-lookup tool from report-running siblings like ga_run_report, though no sibling is named explicitly.

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?

Usage is only implied — one infers you call this to discover field names before building a report. There is no explicit when-to-use, no statement of what to do instead if you already know the field names, and no mention of prerequisites such as needing a property ID format.

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