Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

audit_container

Inspect a GTM workspace for common analytics implementation issues and return structured findings by severity. Read-only audit flags errors, warnings, and optional info without changing anything.

Instructions

Inspect a GTM workspace for common analytics implementation issues. Returns structured findings with severity levels (error/warning/info). This is a read-only operation — it never modifies anything.

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>",
      "containerId": "<containerId>",
      "workspaceId": "<workspaceId>"
    },
    "name": "audit_container"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountIdYes
containerIdYes
includeInfoNoInclude informational findings (verbose). Default: false.
workspaceIdYes

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+$"
    • addedInput schema / properties / containerId / pattern
      Added value: +"^\\d+$"
    • addedInput schema / properties / workspaceId / pattern
      Added value: +"^\\d+$"
  2. Addedv1.421.0
  3. Removedv1.350.0
  4. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description does useful work by declaring 'This is a read-only operation — it never modifies anything', which is exactly the safety context an agent needs. However, it does not disclose permission requirements, whether the audit covers the whole container or only the named workspace, runtime cost, or the structure of the returned findings beyond the three severity levels.

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?

Three short sentences with zero filler: purpose first, output shape second, safety guarantee third. Every sentence earns its place and the most decision-relevant information is front-loaded.

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 read-only inspection tool with no output schema and four parameters at 25% schema coverage, the description is adequate but thin. It says findings come back with severity levels, yet never enumerates the categories of issues checked or explains the scope of the three ID parameters, leaving real gaps an agent cannot fill from structured fields.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 25% — only includeInfo is documented in the schema, while accountId, containerId and workspaceId carry nothing but a numeric pattern. The description adds no meaning to any parameter, not even clarifying that includeInfo controls verbosity of the findings list, so it fails to compensate for the coverage gap.

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?

The description states a specific verb and resource: 'Inspect a GTM workspace for common analytics implementation issues', and adds that it returns structured findings with severity levels. That distinguishes it from read siblings like containers_get or export_container, though it does not name any of them explicitly.

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 rather than stated: an agent can infer this is the diagnostic tool for finding implementation problems, but there is no explicit when-to-use, when-not-to-use, or routing to an alternative such as export_container or containers_get. No prerequisites or preconditions are mentioned.

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