Skip to main content
Glama
Google Growth MCP

Google Growth MCP

by kremnyi

gtm_get_entity

Read-onlyIdempotent

Retrieve a single Google Tag Manager tag, trigger, or variable by full v2 path to inspect its fingerprint and configuration before making changes.

Instructions

Get one GTM tag, trigger, or variable including its fingerprint and configuration.

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": {
      "entity_path": "<entity_path>"
    },
    "name": "gtm_get_entity"
  }
}

Input Schema

NameRequiredDescriptionDefault
entity_pathYesFull GTM v2 path for a tag, trigger, or variable.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered without the description. The description does add that the response includes the entity's fingerprint and configuration, which is real value given there is no output schema, but it says nothing about behavior on a missing or malformed path.

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?

One short sentence with the payload statement front-loaded and no filler. It is efficient, though the terseness means the single sentence carries every dimension of guidance on its own.

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 one-parameter read with no output schema, the definition covers the essentials plus the notable fact that fingerprint and configuration come back. It stops short of describing what those fields look like or how errors surface, which leaves modest gaps for an agent handling the result.

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 100% and there is a single required parameter whose schema description already defines it as a full GTM v2 path. The description only adds that the path may target a tag, trigger, or variable, which is minor reinforcement rather than new syntax or format detail, so the baseline 3 applies.

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?

"Get one GTM tag, trigger, or variable" states a specific verb and resource, and enumerates the three entity kinds the path may address. The word "one" implicitly contrasts with the list-style siblings, but no sibling is named, so it falls short of explicit differentiation.

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 only implied: an agent can infer this is the single-entity read used after finding a path via gtm_list_entities. There is no explicit when-to-use statement, no mention of prerequisites (auth, workspace/container context), and no guidance on when gtm_get_version or gtm_list_entities would be the better choice.

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