Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

ga4_delete_account_access_binding

Revoke a user's GA4 account access by deleting the specified account access binding; requires explicit confirmation to proceed.

Instructions

[GA4 DELETE] Revoke a user's access to an account (needs analytics.manage.users). Requires GA4_MCP_ENABLE_DELETES=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>",
      "confirm": "<confirm>"
    },
    "name": "ga4_delete_account_access_binding"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 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*$"
  2. 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 burden and does disclose the permission required plus two safety gates (server-side deletes flag and confirm=true), which is meaningful context for a destructive operation. It omits whether revocation is irreversible, what happens if the binding is absent, and what the call returns.

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?

A single dense sentence with the destructive tag and action front-loaded, followed by prerequisites. Minimal waste; the bracketed [GA4 DELETE] prefix is mildly redundant with the tool name but reinforces the operation type.

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 2-parameter mutation tool with no output schema and 100% schema coverage, the description supplies the required permission and both enablement gates, which is what an agent needs to attempt the call. Only the irreversibility/error semantics are missing.

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% and the schema already documents both `name` (with a regex for accounts/{account}/accessBindings/{id}) and `confirm`. The description only restates the confirm requirement and adds no extra semantics about the resource-name format.

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 a specific verb and resource: "Revoke a user's access to an account", plus the exact resource type (account access binding) that separates it from the property-level delete sibling. An agent can distinguish it from create/update binding tools without opening any schema.

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 concrete preconditions for use: the analytics.manage.users permission, the GA4_MCP_ENABLE_DELETES=true environment gate, and confirm=true. It stops short of explicitly naming alternatives (e.g. property access binding deletion) or stating when not to use it, so it is clear context rather than full when/when-not routing.

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