Skip to main content
Glama
Google Growth MCP

Google Growth MCP

by kremnyi

gtm_list_workspaces

Read-onlyIdempotent

Lists all workspaces in a specified Google Tag Manager container so you can inspect workspace IDs before managing tags or changes.

Instructions

List workspaces in one GTM container.

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": {
      "container_path": "<container_path>"
    },
    "name": "gtm_list_workspaces"
  }
}

Input Schema

NameRequiredDescriptionDefault
container_pathYesaccounts/{account}/containers/{container}

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, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully carried by structured data. The description adds nothing beyond that: no pagination behavior, no indication of what fields a workspace record contains, and no note on permissions or errors for an invalid container 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, front-loaded sentence with zero redundant wording. It is lean to the point of terseness, but nothing in it is wasted.

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 simple read-only single-parameter tool with full schema coverage and rich annotations, the description is minimally sufficient. It is thin on return content and pagination, though the absence of an output schema makes some of that less critical.

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% with a single self-documenting container_path, so the baseline is 3. The phrase "one GTM container" reinforces that the path targets a single container rather than a wildcard or multiple parents, a small addition beyond the schema.

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 ("List workspaces") and scopes it to "one GTM container," which separates it from gtm_list_accounts and gtm_list_containers by resource type. It doesn't explicitly name a sibling it is not, but the resource noun is unambiguous.

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?

No when-to-use guidance, no prerequisites, and no mention of alternatives such as gtm_list_containers or gtm_create_workspace. The only usage signal is the required container_path parameter, which the agent must infer means a specific parent container.

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