gtm_get_tagRetrieve complete tag details, including parameters, triggers, and configuration, to inspect or debug Google Tag Manager tags.
Get full details of a specific tag, including all its parameters, triggers, and configuration.
| Name | Required | Description | Default |
|---|---|---|---|
| tag_id | Yes | The GTM tag ID | |
| account_id | Yes | The GTM account ID | |
| container_id | Yes | The GTM container ID | |
| workspace_id | Yes | The GTM workspace ID |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and idempotentHint as true, and destructiveHint false. The description adds value by specifying what kind of details are returned (parameters, triggers, configuration), which is not present in the annotations. This contextualizes the response content without contradicting the annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single, front-loaded sentence that immediately states the tool's purpose and key details. Every word adds value, with no redundancy or fluff. Ideal conciseness.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple GET operation with all required parameters fully documented in the schema, the description sufficiently covers the tool's behavior. No output schema is present, so return values need not be detailed. The description's enumeration of 'parameters, triggers, and configuration' addresses the primary context an agent needs.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with each parameter having a clear description (e.g., 'The GTM tag ID'), so the schema already handles parameter semantics. The description does not need to add more, and the baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb and resource: 'Get full details of a specific tag', which clearly states the action and object. The phrase 'including all its parameters, triggers, and configuration' adds useful scope, and it distinguishes from sibling methods like gtm_list_tags or gtm_get_container.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit guidance on when to use this tool versus alternatives. The description implies it is for retrieving a single tag's full details, but it does not mention when not to use it or compare with gtm_list_tags or gtm_get_trigger. This matches the 'no guidance' level.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.