Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

user_permissions_delete

Revoke a user's access to a Google Tag Manager account by deleting a specific user permission; requires delete enablement and explicit confirmation.

Instructions

[DELETE] Revoke a user's access to a GTM account. Requires GTM_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": {
      "accountId": "<accountId>",
      "userPermissionId": "<userPermissionId>",
      "confirm": "<confirm>"
    },
    "name": "user_permissions_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true to confirm this delete operation.
accountIdYesThe GTM account ID.
userPermissionIdYesThe user permission ID to delete.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.497.5
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / accountId / pattern
      Added value: +"^\\d+$"
    • addedInput schema / properties / userPermissionId / pattern
      Added value: +"^\\d+$"
  2. Addedv1.421.0
  3. Removedv1.350.0
  4. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it does add real value by disclosing the environment-flag gate and the confirm safeguard. It leaves out whether the revocation is reversible, whether the call fails outright when the flag is unset, and what happens to the user's remaining roles, which matters for an irreversible mutation.

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, zero filler, with the destructive nature flagged up front in brackets and the hard prerequisites immediately after. Every element earns its place.

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, non-nested delete with no output schema and no annotations, the definition covers the essentials: scope, gating flag, and confirmation. What is missing is only secondary detail about failure behavior and the effect on the user's other access, so it is nearly complete rather than fully complete.

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 accountId, userPermissionId, and confirm are all documented in the schema itself. The description only restates the confirm=true requirement, adding no format, ID-source, or edge-case meaning beyond structured data; baseline 3 applies.

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?

The description pairs a bracketed operation marker with a specific verb and resource: "[DELETE] Revoke a user's access to a GTM account." An agent can immediately tell this targets a user-permission grant rather than the account, client, environment, or tag deletion siblings, without opening the 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?

It states the preconditions an agent must satisfy before calling: the GTM_MCP_ENABLE_DELETES=true server flag and confirm=true in the request. It does not name an alternative or spell out when-not-to-use (e.g., prefer user_permissions_update to downgrade access), so it stops short of full routing guidance.

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