Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

ga4_archive_audience

Archives a GA4 audience to stop data collection permanently. Use it when an audience is no longer needed; no un-archive is available, and confirmation is required.

Instructions

[GA4 DELETE] Archive an audience (stops collection; effectively permanent). 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_audience"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesFull resource name of the audience to target: "properties/{property}/audiences/{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 audience to target, e.g. \"properties/123/…/456\"."New value: +"Full resource name of the audience to target: \"properties/{property}/audiences/{id}\"."
    • removedInput schema / properties / name / minLength
      Removed value: -1
    • addedInput schema / properties / name / pattern
      Added value: +"^\\s*properties\\/\\d+\\/audiences\\/[A-Za-z0-9_-]+\\s*$"
  2. Addedv1.160.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses irreversibility ('no un-archive'), that collection stops, and the environment/confirm gates. It omits what happens to historical audience membership or the response, which are the remaining gaps.

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?

It is short and front-loaded, leading with the delete tag and the core effect. The only flaw is redundancy: 'effectively permanent' appears twice in two sentences.

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 mutation tool with no annotations or output schema, the description covers the essential risks: permanence, no un-archive, the delete-toggle guard, and the confirm gate. It lacks only the response shape and data-retention behavior, which are minor for a call decision.

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 documented there, including the resource-name pattern. The description only restates the confirm=true requirement and adds no new syntax or format detail, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('Archive an audience') and adds scope ('stops collection'), plus a '[GA4 DELETE]' tag that separates it from ga4_create_audience and ga4_update_audience. An agent can pick it out of the sibling list without opening the schema.

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?

It states preconditions clearly: deletes must be enabled via GA4_MCP_ENABLE_DELETES=true and confirm=true is required. It implies permanence discourages casual use, but never explicitly contrasts with update_audience or says when not to archive, so it stops short of full routing guidance.

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