Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

containers_lookup

Find the Google Tag Manager container linked to a destination ID, such as a GA4 measurement ID or tag ID, to identify the correct container for audits or configuration checks.

Instructions

Look up a GTM container by its linked destination ID (e.g. a GA4 measurement ID or tag ID).

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": {
      "destinationId": "<destinationId>"
    },
    "name": "containers_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
destinationIdYesThe destination/tag ID to look up (e.g. "G-XXXXXXX").

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.497.5
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.0.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are supplied, so the description must carry the behavioral burden. 'Look up' implies a read-only query, but the description does not state permissions, whether the match is exact, what happens on zero or multiple matches, or what is returned.

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?

It is a single front-loaded sentence with no filler. The parenthetical examples directly support the lookup key and do not bloat the definition.

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 one-parameter lookup, the definition gives enough to invoke the tool correctly: the resource, the key type, and examples. It is thinner on return behavior and alternatives to use, but the low complexity and strong schema coverage keep it reasonably complete.

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

Parameters4/5

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

Schema description coverage is 100%, giving a baseline of 3. The description adds useful meaning by saying the input is a linked destination ID and by giving GA4 measurement ID or tag ID examples, beyond the schema's generic destination/tag ID wording.

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: 'Look up a GTM container.' It also narrows the lookup key to a linked destination ID, which helps distinguish it from generic container retrieval. However, it does not explicitly name or contrast it with siblings such as containers_get or containers_list.

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?

The definition implies usage when the caller has a destination/tag ID rather than a container ID, but it gives no explicit when-to-use, when-not-to-use, or alternative-tool guidance. An agent has to infer routing from the parameter.

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