Skip to main content
Glama

GA4 metrics

analytics_get_ga4_metrics
Read-only

GA4 traffic and conversions for this account.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "analytics_get_ga4_metrics"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNo
daysNo
limitNo
actionNo
statusNo
date_toNo
page_idNo
sort_byNo
user_idNo
site_urlNo
client_idNo
date_fromNo
ad_accountNo
ig_user_idNo
user_emailNo
range_presetNo
activity_onlyNo
campaign_nameNo
property_nameNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / action
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Action"
      +}
    • addedInput schema / properties / status
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Status"
      +}
  2. First observed

TDQS

C2.1/5.0
Behavior2/5

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

Annotations already establish that this is a read-only, non-open-world operation, so the description does not need to repeat safety traits. However, it adds little behavioral context beyond 'for this account'β€”it does not explain what 'this account' means, how data is aggregated, whether values are cached or live, or what the response contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is front-loaded and contains no filler, but it is drastically under-sized for a tool with 19 undocumented parameters. Conciseness is technically good, yet the sentence does very little work toward making the tool invokable.

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

Completeness1/5

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

Given 19 parameters, no required fields, zero schema descriptions, and only minimal annotations, the description is far too sparse to make this tool usable. The output schema relieves the need to explain return values, but the input side and usage context are almost entirely undocumented.

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

Parameters1/5

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

The tool has 19 parameters with 0% schema description coverage, and the description provides no information about any of them. Ambiguous parameters such as action, status, range_preset, activity_only, property_name, and ad_account remain completely undefined, so the description does not compensate for the schema gap.

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

Purpose3/5

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

The description states the resource domain ('GA4 traffic and conversions') but uses a noun phrase rather than a verb like 'retrieve' or 'query,' leaving the operation slightly ambiguous. It does not distinguish this tool from sibling analytics tools such as analytics_get_ai_referrals, analytics_get_checkout_funnel, or analytics_get_organic_roi.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives. With many sibling analytics tools available, an agent must infer that this one is for GA4 traffic and conversion metrics, but nothing states that explicitly or explains any prerequisites.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.