Google Tag Manager MCP Server

create_container

Create a new Google Tag Manager container to organize and deploy tracking tags, triggers, and variables for websites or mobile apps.

Instructions

新しいコンテナを作成します

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

Input Schema

Name	Required	Description
`accountId`	Yes	アカウントID
`name`	Yes	コンテナ名
`usageContext`	Yes	使用コンテキスト（例: ["web"]）

Schema Changelog

Changes observed during successful MCP inspections.

First observedDec 31, 2025

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. '作成します' (creates) implies a write operation, but the description doesn't disclose any behavioral traits such as permissions required, whether creation is idempotent, rate limits, or what happens on success/failure. For a mutation tool with zero annotation coverage, this is a significant gap.

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?

The description is a single, efficient sentence in Japanese that directly states the tool's purpose. It's appropriately sized and front-loaded with no unnecessary words or structural issues.

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?

Given this is a mutation tool (creating a container) with no annotations and no output schema, the description is incomplete. It doesn't explain what a container is in this context, what the creation entails, or what to expect as a result. The agent lacks crucial context for proper tool invocation despite the good schema coverage.

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?

The description adds no parameter information beyond what the input schema provides. Schema description coverage is 100%, with all three parameters (accountId, name, usageContext) documented in the schema. The baseline score of 3 is appropriate as the schema does the heavy lifting, but the description doesn't add any contextual meaning about parameters.

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 '新しいコンテナを作成します' (creates a new container) clearly states the action (creates) and resource (container). It distinguishes from siblings like 'get_container' or 'list_containers' by specifying creation rather than retrieval. However, it doesn't specify what type of container or differentiate from other creation tools like 'create_tag' or 'create_variable' beyond the resource name.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., authentication), when not to use it, or how it relates to sibling tools like 'get_container' or 'list_containers'. The agent must infer usage from the name alone.

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