Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

ga4_create_property

Creates a new GA4 property under an existing account. Use it to provision analytics properties with a display name, IANA time zone, and ISO 4217 currency, gated by write opt-in and per-call confirmation.

Instructions

[GA4 WRITE] Create a new GA4 property under an account. Requires GA4_MCP_ENABLE_WRITES=true and confirm=true.

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>",
      "displayName": "<displayName>",
      "timeZone": "<timeZone>",
      "currencyCode": "<currencyCode>",
      "confirm": "<confirm>"
    },
    "name": "ga4_create_property"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYes
timeZoneYesIANA time zone, e.g. "America/New_York".
accountIdYesParent account ID ("123456" or "accounts/123456").
displayNameYes
currencyCodeYesISO 4217 currency, e.g. "USD".
industryCategoryNoe.g. "TECHNOLOGY", "RETAIL".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 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*$"
  2. Addedv1.160.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the most important gating behavior — the environment write flag and confirm flag — but says nothing about irreversibility, resulting property state, quotas, or permission requirements of the underlying account.

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 plus a bracketed write tag; the tag aids fast scanning and the requirement is front-loaded after the action. Nothing is padded, though the prerequisite sentence is terse enough that it reads like a hint rather than full guidance.

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 six-parameter write tool with no annotations and no output schema, the definition covers the critical risk (write gating) that an agent must satisfy before calling. It is missing only the return shape (new property resource name/ID) that an agent would want in order to chain into data-stream or access-binding creates.

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 67%, with accountId, timeZone, and currencyCode documented in-schema. The description adds genuine meaning for 'confirm' (schema only declares it as an untyped boolean role) by stating it must be true, but leaves displayName and industryCategory unelaborated.

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 ('Create a new GA4 property') and adds the parent scope ('under an account'), which separates it from sibling creates such as ga4_create_data_stream or ga4_create_property_access_binding. It never names an adjacent tool (e.g., ga4_update_property) to sharpen the boundary, so it stops short of a 5.

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?

The definition gives an actionable precondition pair (GA4_MCP_ENABLE_WRITES=true and confirm=true), which is real usage guidance for invocation. However, it offers no when/when-not guidance relative to alternatives like ga4_update_property or ga4_create_account, and no note on what to do if the write flag is disabled.

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