Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

ga4_check_compatibility

Checks whether GA4 dimensions and metrics can be combined in one report, helping you drop incompatible fields before running a Data API query.

Instructions

Check which of the given GA4 dimensions/metrics can be combined in ONE report on this property (the Data API rejects incompatible pairs). Call this BEFORE ga4_run_report when combining unusual dimensions/metrics; drop or replace anything reported incompatible instead of retrying blind. Read-only.

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

Input Schema

NameRequiredDescriptionDefault
metricsNoMetric API names to test.
propertyYesGA4 property ID, e.g. "123456789" or "properties/123456789".
dimensionsNoDimension API names to test.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.497.5
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / property / minLength
      Removed value: -1
    • addedInput schema / properties / property / pattern
      Added value: +"^\\s*(properties\\/)?\\d+\\s*$"
  2. Addedv1.421.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are supplied, so the description must carry the behavioral load, and it does declare read-only plus the underlying API failure mode. It stops short of describing what an incompatibility result looks like or how failures are surfaced, leaving the response shape undefined.

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

Conciseness5/5

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

Three short sentences, each doing distinct work: what it checks, when to call it, and what to do with the result. The precondition is front-loaded and there is no filler.

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?

For a three-parameter read-only validation tool with no output schema, the description covers purpose, timing, and remediation well. The main remaining gap is the return value: an agent cannot tell whether incompatible items come back as a list, a flag, or an error message.

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 three parameters are already documented in the schema with formats and examples. The description only refers generically to 'given GA4 dimensions/metrics' and 'this property', adding no syntax or constraint detail beyond the schema.

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 and resource: checking whether given GA4 dimensions/metrics can be combined in one report on a property. It also explains why the check exists (the Data API rejects incompatible pairs), which distinguishes it from the sibling ga4_run_report.

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

Usage Guidelines5/5

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

Explicitly says to call this BEFORE ga4_run_report when combining unusual dimensions/metrics, and prescribes the follow-up action: drop or replace incompatible items instead of retrying blind. Both the trigger condition and the alternative are named.

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