Skip to main content
Glama
Google Growth MCP

Google Growth MCP

by kremnyi

gtm_create_entity

Creates a Google Tag Manager tag, trigger, or variable in a workspace after explicit user confirmation, so approved GTM changes are applied safely.

Instructions

Create a GTM tag, trigger, or variable in a workspace. Requires explicit user confirmation.

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": {
      "workspace_path": "<workspace_path>",
      "entity_type": "<entity_type>",
      "entity": "<entity>",
      "change_summary": "<change_summary>",
      "user_confirmed": "<user_confirmed>"
    },
    "name": "gtm_create_entity"
  }
}

Input Schema

NameRequiredDescriptionDefault
entityYesGTM API Tag, Trigger, or Variable body.
entity_typeYes
change_summaryYesConcise exact change the user approved in the current request.
user_confirmedYesMust be true only after explicit action-time user confirmation.
workspace_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the meaningful behavioral gate 'requires explicit user confirmation,' but says nothing about what happens on success (returned ID, whether the workspace becomes dirty) or what errors are surfaced for a non-idempotent remote write.

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?

Two sentences, zero filler, and the most important constraint (the confirmation requirement) is placed immediately after the purpose statement. Nothing is redundant with the title or schema.

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 non-idempotent remote mutation with a nested object parameter and no output schema, the description covers purpose and the confirmation gate but leaves out post-creation state (does the workspace need gtm_sync_workspace or gtm_create_version next?) and error behavior. Adequate but with clear gaps for a tool of this complexity.

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 coverage is 60%, and the schema already documents change_summary, user_confirmed, and the entity_type enum well. The description only reinforces workspace scoping and entity kinds; it adds no meaning about the nested entity body shape or the workspace_path format, so it neither compensates for nor worsens 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?

States a specific verb and resource — create a GTM tag, trigger, or variable — and scopes it to a workspace, which an agent can distinguish from gtm_update_entity or gtm_delete_entity by name alone. It does not explicitly disambiguate itself from gtm_create_version or gtm_create_workspace, 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 Guidelines3/5

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

Usage is implied by the verb 'create' and the 'in a workspace' scoping, and the confirmation precondition is stated. However, there is no guidance on when to use this versus gtm_update_entity (existing entity) or when a new workspace/version is needed first, and no failure conditions are described.

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