Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

user_permissions_create

Grants a user access to a Google Tag Manager account and optionally sets per-container permissions; requires explicit confirmation for the write.

Instructions

[WRITE] Grant a user access to a GTM account (and optionally containers). Requires GTM_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": {
      "accountId": "<accountId>",
      "emailAddress": "<emailAddress>",
      "confirm": "<confirm>"
    },
    "name": "user_permissions_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true to confirm this write operation.
accountIdYesThe GTM account ID.
emailAddressYesEmail address of the user to grant access to.
containerAccessNoPer-container access entries.
accountPermissionNoAccount-level permission.

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.8/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 behavioral burden and does add real value: it labels the call as a write, names the environment gate GTM_MCP_ENABLE_WRITES=true, and states the confirm=true safety requirement. It stops short of disclosing effects on an already-existing user (overwrite vs. error), whether notifications are sent, or failure modes.

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 sentences, zero filler, with the [WRITE] classification and the core action front-loaded before the prerequisites. Every clause carries information the agent needs.

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 five-parameter write tool with full schema coverage and no output schema, the definition covers the essential operator concerns: it is a write, it needs a feature flag, and it needs confirmation. The remaining gap is post-call behavior and treatment of pre-existing users, which no structured field covers.

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 every parameter including accountPermission, containerAccess entries, and confirm is already documented in the schema, making 3 the baseline. The description adds only the high-level framing that account access is primary and container access optional, without clarifying permission-level semantics beyond the enum descriptions.

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?

Specific verb plus resource: "Grant a user access to a GTM account (and optionally containers)", with a [WRITE] prefix that immediately classifies the operation. It is clearly distinct in kind from read-oriented siblings such as user_permissions_get/user_permissions_list, but it does not explicitly contrast itself with user_permissions_update or user_permissions_delete.

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

Usage Guidelines3/5

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

Usage is implied by "Grant a user access" and made concrete by the stated prerequisites (GTM_MCP_ENABLE_WRITES=true and confirm=true). However, there is no explicit guidance on when to choose this over user_permissions_update (e.g., existing user with changed permissions) or delete, so the agent must infer the boundary.

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