Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

ga4_properties_list

List all GA4 properties under a parent account and return full property records, including display name, time zone, currency, industry, and service level. Read-only.

Instructions

List GA4 properties under a given parent account. Returns full property records (display name, time zone, currency, industry, service level). 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": {
      "accountId": "<accountId>"
    },
    "name": "ga4_properties_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.
accountIdYesParent GA4 account ID, e.g. "123456" or "accounts/123456".
pageTokenNoContinuation token to resume listing from a previous truncated result.
showDeletedNoInclude soft-deleted (trashed) properties in the results.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.497.5
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / accountId / minLength
      Removed value: -1
    • addedInput schema / properties / accountId / pattern
      Added value: +"^\\s*(accounts\\/)?\\d+\\s*$"
    • addedInput schema / properties / maxPages / maximum
      Added value: +9007199254740991
  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, the description carries the burden, and it does disclose 'Read-only' plus the shape of returned records. It omits pagination/truncation behavior (which lives only in the schema) and says nothing about permission requirements or how soft-deleted properties behave, so the behavioral picture is only partially filled in.

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?

Two short sentences, front-loaded with the action and scope, followed by the return contents and a read-only marker. No filler or redundant restatement of the title.

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 described parameters and no output schema, the description covers what it returns and that it is non-mutating. The only real gap is pagination behavior, which the schema already handles.

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 four parameters are already documented, including pageToken, maxPages and showDeleted. The description reinforces that listing is scoped to a parent account but adds no syntax or format detail beyond what the schema provides, so the baseline 3 applies.

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 GA4 properties') and scopes it to a parent account, plus enumerates the returned fields (display name, time zone, currency, industry, service level). That clearly separates it from sibling list tools like ga4_data_streams_list or ga4_custom_dimensions_list, though it never explicitly contrasts with the closest sibling ga4_account_summaries_list.

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 infers this is the tool to call when it has an account ID and needs its properties. There is no explicit when-to-use/when-not-to-use guidance and no mention of the alternative account-level tools that could be confused with it.

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