Skip to main content
Glama

List Tag Manager containers

tag_manager_containers
Read-only

Lists Google Tag Manager web containers your Google login can access so you can select one for Tag Manager tasks or create a container; returns a grant link if access isn't connected.

Instructions

Lists the Google Tag Manager web containers this Google login can read. Use a container from here in the other Tag Manager tools, and an account_id to create a container in (create_container). If Tag Manager isn't part of the connection yet, says so and returns grant_url, a personal link the user opens to add it.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tag_manager_containers"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.32.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the read-only, non-destructive, open-world profile, so the description's value is what it adds: the result set is permission-scoped to the login, and when Tag Manager is not yet connected the tool reports that and returns a grant_url the user must open to authorize. That OAuth fallback behavior is genuinely beyond what the structured fields convey.

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?

Three sentences, front-loaded with the core action, then usage routing, then the edge-case behavior. Every sentence carries information; the final sentence is slightly dense (mixing the 'not connected' condition with the grant_url mechanic) but still readable.

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?

There is no output schema, so the description must hint at return shape — it names containers and the grant_url fallback, which is enough. For a zero-parameter listing tool this covers the essentials, though it says nothing about ordering or whether pagination applies.

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?

With zero parameters the baseline is 4, and the description correctly adds nothing spurious to the schema. It does mention account_id, but explicitly in the context of the create_container sibling rather than as an input here, which is mildly ambiguous but not misleading.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource — 'Lists the Google Tag Manager web containers' — and adds a scope qualifier ('this Google login can read'). No sibling tool lists containers, so there is no ambiguity about which tool to reach for when the goal is container discovery.

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

Usage Guidelines4/5

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

It states what to do with the results ('Use a container from here in the other Tag Manager tools') and routes the create path to create_container along with the account_id it needs. The only gap is that it does not explicitly say 'do not call this if you already have a container ID,' but the intended flow is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.