Skip to main content
Glama
Google Growth MCP

Google Growth MCP

by kremnyi

gtm_delete_workspace

Destructive

Delete a Google Tag Manager workspace only after explicit user confirmation, with a required change summary to verify the exact approved action.

Instructions

Delete a GTM workspace. Requires explicit confirmation of this exact deletion.

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>",
      "change_summary": "<change_summary>",
      "user_confirmed": "<user_confirmed>"
    },
    "name": "gtm_delete_workspace"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is known. The description adds the meaningful gate that the agent must obtain explicit action-time user confirmation for this exact deletion, but it never says whether the deletion is irreversible, what happens to the workspace's contents, or whether dependent entities/versions are affected.

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?

Two short sentences, front-loaded with the action and followed by the gating constraint; nothing is padded. The second sentence is slightly vague ('explicit confirmation of this exact deletion') relative to what the schema already spells out.

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 destructive, non-idempotent, open-world tool with three required parameters and no output schema, the description covers the confirmation requirement but omits irreversibility and blast-radius information an agent would want before calling it. Adequate, but with a clear gap on the highest-risk dimension.

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 67%: change_summary and user_confirmed are documented in the schema, while workspace_path has no description anywhere. The sentence about explicit confirmation reinforces the intent of user_confirmed but adds no syntax or format detail for the undocumented path parameter, so it sits at the baseline.

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 and resource ('Delete a GTM workspace'), which separates it from siblings like gtm_delete_entity or gtm_create_workspace by resource alone. It never names an alternative explicitly, 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 Guidelines2/5

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

It states a precondition ('Requires explicit confirmation of this exact deletion') but gives no guidance on when to use this versus gtm_delete_entity or any other destructive sibling, and no exclusion or prerequisite context beyond confirmation.

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