Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

user_permissions_get

Retrieve a specific user permission record for a Google Tag Manager account by account ID and user permission ID to verify access details.

Instructions

Get a specific user permission record for a GTM account.

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>"
    },
    "name": "user_permissions_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountIdYesThe GTM account ID.
userPermissionIdYesThe user permission ID.

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

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. "Get" implies a non-destructive read, but the definition says nothing about required GTM admin permissions, behavior when the ID does not exist, or what the returned record contains — notable gaps for a permissions-related tool where access requirements matter.

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?

A single front-loaded sentence with zero wasted wording; the verb, specificity, and resource scope all arrive before the trailing account qualifier.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read tool with fully described parameters and no output schema, the description is minimally sufficient to identify and call it. It leaves the return shape and failure semantics unstated, though the absence of an output schema makes that a modest omission.

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%, with both accountId and userPermissionId documented in the schema itself, so the baseline of 3 applies. The description's phrase "for a GTM account" only loosely reinforces the accountId linkage and adds no format, ID-discovery, or constraint detail beyond 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 specific verb and resource ("Get a specific user permission record") and scopes it to a GTM account, which distinguishes it from the list/create/update/delete siblings implied by the singular-record framing. It stops short of explicitly naming the list or search alternative an agent would use when it lacks an ID.

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 only implied: an agent can infer it should call this when it already has both an accountId and a userPermissionId. There is no explicit statement of when not to use it, no pointer to user_permissions_list for enumeration, and no mention of prerequisites such as admin access.

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