Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

accounts_get

Retrieve details for a specific Google Tag Manager account using its numeric account ID to inspect account settings and verify the correct GTM account before container audits or configuration.

Instructions

Get details of a specific 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>"
    },
    "name": "accounts_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountIdYesThe GTM account ID (numeric string).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.497.5
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / accountId / pattern
      Added value: +"^\\d+$"
  2. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/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. 'Get' implies a read-only, non-destructive operation, but the description says nothing about what fields are returned, permissions/authentication needed, or what happens with an invalid or unknown account ID. For a tool with zero annotation coverage, this leaves meaningful gaps.

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?

One short sentence, front-loaded with the verb and resource, with no filler or redundant restatement. There is nothing superfluous, though there is also nothing surplus that would earn a 5.

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 one-parameter read tool with no output schema and full schema coverage, the description covers the core intent. It is missing return-content expectations and error behavior, which are more relevant here precisely because no annotations or output schema backfill them.

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%: the single accountId parameter is documented in-schema as a numeric string with an enforced pattern. The description adds no meaning beyond that, so the baseline score of 3 applies.

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 details of a specific GTM account.' The word 'specific' signals this is a single-item fetch rather than a listing, which implicitly separates it from accounts_list. It stops short of naming the sibling or stating exactly what 'details' comprise, so it is clear but not fully differentiated.

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 infers 'use this when you have one account ID and want that account.' There is no explicit when-to-use versus accounts_list, and no stated prerequisite such as needing a valid numeric ID first. Adequate for a trivial getter, but the routing guidance is left to inference.

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