Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

ga4_create_property_access_binding

Grant a user access to a GA4 property by assigning roles like viewer, analyst, editor, or admin. Requires write mode enabled and per-call confirmation.

Instructions

[GA4 WRITE] Grant a user access to a GA4 property (needs analytics.manage.users scope). 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": {
      "property": "<property>",
      "user": "<user>",
      "roles": "<roles>",
      "confirm": "<confirm>"
    },
    "name": "ga4_create_property_access_binding"
  }
}

Input Schema

NameRequiredDescriptionDefault
userYesEmail of the user to grant access to.
rolesYesRoles, e.g. ["predefinedRoles/viewer"], ["predefinedRoles/analyst"], ["predefinedRoles/editor"], ["predefinedRoles/admin"]. (GA4 uses viewer/analyst/editor/admin — not the legacy read/collaborate/edit/manage names.)
confirmYesMust be true to apply the change.
propertyYesGA4 property ID, e.g. "123456789" or "properties/123456789".

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
  3. Removedv1.350.0
  4. Changed1 schema field changedv1.263.0
    • changedInput schema / properties / roles / description
      Previous value: -"Roles, e.g. [\"predefinedRoles/read\"], [\"predefinedRoles/analyst\"], [\"predefinedRoles/editor\"], [\"predefinedRoles/admin\"]."New value: +"Roles, e.g. [\"predefinedRoles/viewer\"], [\"predefinedRoles/analyst\"], [\"predefinedRoles/editor\"], [\"predefinedRoles/admin\"]. (GA4 uses viewer/analyst/editor/admin — not the legacy read/collaborate/edit/manage names.)"
  5. Addedv1.160.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses this is a WRITE, the required OAuth scope (analytics.manage.users), the GA4_MCP_ENABLE_WRITES=true gate, and the mandatory confirm=true — real operational prerequisites an agent cannot infer elsewhere. It stops short of stating reversibility or the error behavior on an existing binding.

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?

One front-loaded sentence with a bracketed WRITE tag, purpose first, prerequisites parenthetical. No filler; every clause carries information an agent needs before invoking.

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 four-required-parameter mutation with no annotations and no output schema, the description plus rich schema gives enough to call it correctly: target, gating flags, scope, and role vocabulary. The only gap is what happens on a pre-existing binding or what the call returns.

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 property, user, roles and confirm are already fully documented, including role naming conventions and the property ID pattern. The description adds nothing about parameters beyond restating confirm=true, so 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 — 'Grant a user access to a GA4 property' — plus the acting scope, so the agent knows exactly which object is mutated and for whom. It does not explicitly distinguish itself from the update/delete access-binding siblings, which keeps it below 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?

Usage is implied by 'Grant a user access' and the write tag, and prerequisites (scope, env flag, confirm) are given. However, it never says when to use this versus ga4_update_property_access_binding, nor what happens if the user already has a binding on that property.

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