Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

ga4_update_account_access_binding

Update a user's GA4 account roles by replacing the access binding's roles; requires write mode and confirmation.

Instructions

[GA4 WRITE] Change a user's roles on an account (needs analytics.manage.users). The roles you pass replace the binding's roles. This API has no updateMask: the supplied fields replace the whole resource. 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": {
      "name": "<name>",
      "roles": "<roles>",
      "confirm": "<confirm>"
    },
    "name": "ga4_update_account_access_binding"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesFull resource name of the account access binding to target: "accounts/{account}/accessBindings/{id}".
rolesYes
confirmYesMust be true to apply the change.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.497.5
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / name / description
      Previous value: -"Full resource name of the account access binding to target, e.g. \"properties/123/…/456\"."New value: +"Full resource name of the account access binding to target: \"accounts/{account}/accessBindings/{id}\"."
    • removedInput schema / properties / name / minLength
      Removed value: -1
    • addedInput schema / properties / name / pattern
      Added value: +"^\\s*accounts\\/\\d+\\/accessBindings\\/[A-Za-z0-9_-]+\\s*$"
    • removedInput schema / properties / updateMask
      Removed value: -{
      -  "description": "Comma-separated field paths to update. Omit to derive from the supplied fields.",
      -  "type": "string"
      -}
  2. Addedv1.160.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the burden: it discloses the required permission, write gating, confirmation requirement, and the crucial replace-not-merge semantics ('roles you pass replace the binding's roles') plus the absence of updateMask. It does not describe error/return behavior or edge cases, but the mutation's main risk is well disclosed.

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?

Four dense sentences, front-loaded with the write tag and purpose; each sentence adds distinct operational information with no wasted wording.

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 three-parameter mutation with no annotations or output schema, it covers permissions, write gating, confirmation, and replacement semantics. It leaves response/return behavior and role validation details unspecified, but is largely complete for safe invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67%; the schema documents name and confirm, while roles has no schema description. The description adds meaning by explaining that roles replace the binding's roles rather than merge, though it does not detail valid role values.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States the specific verb ('Change ... roles') and resource ('account access binding'), and the 'on an account' scope distinguishes it from the property-access-binding update sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear prerequisites (analytics.manage.users, GA4_MCP_ENABLE_WRITES=true, confirm=true) that define when it can be used, but does not explicitly route between create/update/delete siblings or state when not to use 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