Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

ga4_archive_custom_dimension

Archives a GA4 custom dimension permanently when it is no longer needed, since GA4 offers no hard delete or unarchive. Requires confirm=true.

Instructions

[GA4 DELETE] Archive a custom dimension (there is no hard delete). Archiving is effectively permanent (no un-archive). Requires GA4_MCP_ENABLE_DELETES=true and confirm=true.

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": {
      "name": "<name>",
      "confirm": "<confirm>"
    },
    "name": "ga4_archive_custom_dimension"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesFull resource name of the custom dimension to target: "properties/{property}/customDimensions/{id}".
confirmYesMust be true to archive.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.497.5
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / name / description
      Previous value: -"Full resource name of the custom dimension to target, e.g. \"properties/123/…/456\"."New value: +"Full resource name of the custom dimension to target: \"properties/{property}/customDimensions/{id}\"."
    • removedInput schema / properties / name / minLength
      Removed value: -1
    • addedInput schema / properties / name / pattern
      Added value: +"^\\s*properties\\/\\d+\\/customDimensions\\/[A-Za-z0-9_-]+\\s*$"
  2. Addedv1.421.0
  3. Removedv1.350.0
  4. Addedv1.160.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden and does disclose the two most important traits: the operation is irreversible and cannot be undone. It omits what happens to the dimension's collected data after archiving, whether it can be recreated, and the failure mode when confirm is false or the env flag is off.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short clauses, front-loaded with the [GA4 DELETE] tag and the action, then the semantic caveat, then the prerequisites. No redundant wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter irreversible mutation with no output schema, the essentials are covered: what it does, that it cannot be reverted, and the gating conditions. A note on post-archive effects (e.g., data retention, dimension still listed) would complete it.

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 both parameters are self-documenting (regex-constrained resource name, explicit confirm flag). The description reinforces the confirm requirement but adds no format or edge-case detail beyond the schema, so 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?

States a specific verb+resource ('Archive a custom dimension') and immediately disambiguates the semantics by noting there is no hard delete. It does not explicitly route the agent against siblings such as ga4_update_custom_dimension, but the action is unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Gives the precondition for the preferred path (GA4_MCP_ENABLE_DELETES=true and confirm=true) and warns that archiving is effectively permanent with no un-archive, which functions as a when-not-to-use caution. It stops short of naming an alternative tool for reversible edits.

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

Deploy Server

Other Tools