Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

ga4_custom_dimensions_list

Lists custom dimensions configured on a GA4 property, including parameter name, display name, and scope (EVENT/USER/ITEM). Read-only; inspect available dimensions before reporting.

Instructions

List custom dimensions configured on a GA4 property (parameter name, display name, scope: EVENT/USER/ITEM). 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_custom_dimensions_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxPagesNoMaximum number of API pages to fetch (default 50). If more pages remain, the result includes truncated:true and a nextPageToken.
propertyYesGA4 property ID, e.g. "123456789" or "properties/123456789".
pageTokenNoContinuation token to resume listing from a previous truncated result.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.497.5
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / maxPages / maximum
      Added value: +9007199254740991
    • removedInput schema / properties / property / minLength
      Removed value: -1
    • addedInput schema / properties / property / pattern
      Added value: +"^\\s*(properties\\/)?\\d+\\s*$"
  2. Addedv1.421.0
  3. Removedv1.350.0
  4. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description does carry the safety burden and discharges part of it with "Read-only." However, it says nothing about permissions/authentication needs, whether archived dimensions are included, or truncation behavior beyond what the schema already documents for maxPages.

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?

A single front-loaded sentence plus a two-word safety clause; no filler, no restatement of the title, and the return shape is conveyed compactly in a parenthetical.

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 simple read-only list tool with fully documented parameters, the description covers purpose, the primary read-only trait, and the returned field set. The only meaningful gap is not clarifying whether a property with many dimensions will paginate or whether archived entries appear, though the schema partly covers pagination.

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 100%, so all three parameters (property, maxPages, pageToken) are already documented in the input schema, establishing a baseline of 3. The description adds no extra meaning about parameter values or formats beyond the return-field hint.

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?

States a specific verb and resource ("List custom dimensions configured on a GA4 property") and even names the fields returned (parameter name, display name, scope). It is clearly distinguishable from ga4_custom_metrics_list by the resource noun, though it never explicitly contrasts the two.

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: an agent can infer this is the discovery/read path before ga4_create_custom_dimension or ga4_update_custom_dimension, but the description never says when to prefer it over archiving or metric-related siblings. No exclusions or prerequisites are given.

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