Skip to main content
Glama
Google Growth MCP

Google Growth MCP

by kremnyi

gtm_list_entities

Read-onlyIdempotent

Lists tags, triggers, or variables in a Google Tag Manager workspace so you can inspect configured entities before making changes.

Instructions

List tags, triggers, or variables in a GTM workspace.

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

Input Schema

NameRequiredDescriptionDefault
entity_typeYes
workspace_pathYesaccounts/{account}/containers/{container}/workspaces/{workspace}

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile requires nothing from the description. The description adds no behavioral context beyond the annotations — nothing about result ordering, volume, pagination, or what an empty workspace returns.

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?

A single front-loaded sentence with no filler, and the resource list appears before the scope qualifier. It is efficient, though the brevity leaves no room for the usage and behavioral detail the definition otherwise lacks.

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?

This is a simple two-parameter read tool whose annotations cover the safety profile, so completeness demands are modest. However, with no output schema the description should describe what a listing returns (item shape, whether full entity bodies or summaries) and it does not, leaving a meaningful gap for an agent deciding whether to list or fetch.

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 50%: workspace_path carries its own path-template description and entity_type is self-documenting via its enum. The description's enumeration of 'tags, triggers, or variables' merely restates the enum values rather than adding format, casing, or defaulting semantics, so it sits at the stated baseline for partially covered schemas.

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 gives a specific verb ('List') and names the exact resources ('tags, triggers, or variables') plus the containing scope ('in a GTM workspace'), which separates it from gtm_get_entity and gtm_list_workspaces. It stops short of explicitly naming the sibling that should be used instead for container- or account-level listings.

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?

There is no when-to-use or when-not-to-use guidance, no prerequisite statement (e.g. that the workspace path must already exist), and no reference to alternatives such as gtm_get_entity for a single item. The agent must infer the selection context entirely from the tool name and siblings.

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