Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

ga4_update_property_access_binding

Change a user's roles on a GA4 property access binding. Supplied roles replace existing ones; requires writes enabled and confirmation.

Instructions

[GA4 WRITE] Change a user's roles on a property (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_property_access_binding"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesFull resource name of the property access binding to target: "properties/{property}/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 property access binding to target, e.g. \"properties/123/…/456\"."New value: +"Full resource name of the property access binding to target: \"properties/{property}/accessBindings/{id}\"."
    • removedInput schema / properties / name / minLength
      Removed value: -1
    • addedInput schema / properties / name / pattern
      Added value: +"^\\s*properties\\/\\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.421.0
  3. Removedv1.350.0
  4. Addedv1.160.0

TDQS

A4.1/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 disclosure burden and does it well: it flags the write nature, the required OAuth scope, the environment gate, and the confirm flag, and warns that there is no updateMask so the supplied fields replace the whole resource. It stops short of describing reversibility or the response body.

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?

Three tight sentences, front-loaded with the write tag and the permission requirement, then the replacement caveat, then the invocation preconditions. No filler and nothing buried.

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 output schema and no annotations, it covers permission, gating flag, confirm, and replacement behavior — enough to call it safely. Minor gaps are the unchanged behavior for omitted roles and any description of the response.

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% — 'name' and 'confirm' are documented in the schema, but 'roles' is a bare array with no description. The description compensates by explaining that the supplied roles fully replace the binding's existing roles, which is exactly the semantic an agent needs and cannot derive from the schema.

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 concrete verb and resource: 'Change a user's roles on a property,' and the leading '[GA4 WRITE]' tag marks it as a mutation. The 'on a property' scoping implicitly separates it from the account-level binding sibling, though no sibling is named explicitly.

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 context for invocation: requires the analytics.manage.users permission, GA4_MCP_ENABLE_WRITES=true, and confirm=true. It does not explicitly say when to prefer this over create/delete binding, but the replacement semantics make the intent (modify an existing binding) obvious.

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