Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

ga4_delete_property_access_binding

Revoke a user's access to a GA4 property by deleting the specified property access binding, with confirmation required.

Instructions

[GA4 DELETE] Revoke a user's access to a property (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_property_access_binding"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesFull resource name of the property access binding to target: "properties/{property}/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 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*$"
  2. Addedv1.160.0

TDQS

A4.2/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 declares the operation destructive ('revoke'), names the required OAuth scope, and discloses a server-side feature-flag gate plus a mandatory confirm argument. It stops short of saying whether the revocation is reversible or how to re-grant access, which would be the final piece for a delete.

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?

Two short sentences, front-loaded with the action and resource, then the gating requirements. Every clause carries information; there is no filler or restatement.

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 destructive two-parameter tool with no annotations and no output schema, the definition covers the essentials an agent needs to call it safely: permission, feature flag, and confirmation. Only the post-condition (what the response contains, and how to undo) is left unaddressed.

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 both parameters (including the `name` format and the confirm requirement) are already fully documented in the schema. The description adds only the confirm=true gate, which the schema also states, so nothing meaningful is added beyond structured data.

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 a property'. The 'property' scope plus the '[GA4 DELETE]' tag distinguishes it from the sibling account-level binding deletes and from create/update binding tools without needing to open a 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 legitimate use: the analytics.manage.users permission, GA4_MCP_ENABLE_DELETES=true, and confirm=true. It does not explicitly name alternatives (e.g. update vs revoke, account-level binding), so the when-not guidance is left implicit rather than stated.

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