Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

ga4_create_account_access_binding

Grants specified roles to a user on a GA4 account by creating an access binding, requiring write mode enabled and explicit confirmation.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
userYes
rolesYes
confirmYesMust be true to apply the change.
accountIdYesGA4 account ID, e.g. "123456" or "accounts/123456".

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.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 behavioral burden and does well: it flags the operation as a WRITE, names the required OAuth scope, discloses the environment-level write gate, and requires an explicit confirm flag. It stops short of describing idempotency, overwrite behavior for an existing binding, or failure modes.

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 bracketed qualifier marks the tool as a write operation, followed by a single sentence covering action, resource, permission, and gating requirements. Every clause earns its place with no redundancy.

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 4-parameter all-required mutation with no annotations and no output schema, the definition covers the critical agent-facing facts: write classification, authorization scope, environment gate, and explicit confirmation. The remaining gap is the semantics of the roles array and what the response or side effect on existing access looks like.

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 50%, so the schema documents accountId format and the confirm flag while leaving user and roles as bare types. The description reinforces confirm=true but adds no meaning for the roles array, which is the highest-risk parameter since it has no enum constraint and determines the granted privilege level.

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?

The description states a specific verb and resource: "Grant a user access to a GA4 account," which maps directly to creating an account-level access binding. It implicitly distinguishes itself from the delete/update account-access siblings and from the property-level create tool by naming the scope as the GA4 account, though it never names those alternatives explicitly.

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?

Preconditions for use are stated concretely (analytics.manage.users permission, GA4_MCP_ENABLE_WRITES=true, confirm=true), which tells the agent when the call will succeed. However, there is no guidance on when to prefer this over ga4_update_account_access_binding or ga4_create_property_access_binding, nor any statement about what happens if the user already has access.

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