Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

containers_get

Retrieve details for a specific Google Tag Manager container using its account ID and container ID.

Instructions

Get details of a specific GTM container.

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

Input Schema

NameRequiredDescriptionDefault
accountIdYesThe GTM account ID.
containerIdYesThe GTM container 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 / containerId / pattern
      Added value: +"^\\d+$"
  2. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure and delivers almost nothing beyond the verb. It does not say what is returned, whether missing container IDs error or return null, or whether any permissions are required. "Get" weakly implies a read-only, non-destructive operation but nothing more.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though its brevity leaves little structure for the agent to latch onto.

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

Completeness2/5

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

For a simple two-parameter read tool the schema covers inputs fully, but with no annotations and no output schema the description says nothing about the returned detail set or failure modes. A sentence on what details are included and behavior on unknown IDs would close the gap.

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% and both parameters are documented in-schema with numeric patterns, so the baseline of 3 applies. The description adds no format or relationship context (e.g. that accountId scopes the containerId) beyond what the schema already supplies.

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 container") that an agent can distinguish from containers_list or containers_create by the singular object. It does not explicitly name or contrast with any sibling, so it stops short of a 5.

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

Usage Guidelines2/5

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

Implies retrieval of one container by ID but gives no explicit when-to-use, when-not-to-use, or pointer to alternatives such as containers_list for enumeration. The agent must infer the lookup-vs-list distinction purely from the word "specific".

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