Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

ga4_delete_measurement_protocol_secret

Revoke and delete a GA4 Measurement Protocol secret by specifying its full resource name and confirming the action; requires deletes enabled.

Instructions

[GA4 DELETE] Delete a Measurement Protocol secret (revokes it). 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_delete_measurement_protocol_secret"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesFull resource name of the Measurement Protocol secret to target: "properties/{property}/dataStreams/{stream}/measurementProtocolSecrets/{id}".
confirmYesMust be true to delete.

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 Measurement Protocol secret to target, e.g. \"properties/123/…/456\"."New value: +"Full resource name of the Measurement Protocol secret to target: \"properties/{property}/dataStreams/{stream}/measurementProtocolSecrets/{id}\"."
    • removedInput schema / properties / name / minLength
      Removed value: -1
    • addedInput schema / properties / name / pattern
      Added value: +"^\\s*properties\\/\\d+\\/dataStreams\\/\\d+\\/measurementProtocolSecrets\\/[A-Za-z0-9_-]+\\s*$"
  2. Addedv1.421.0
  3. Removedv1.350.0
  4. Addedv1.160.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations supplied, the description carries the safety burden and does so: it flags a destructive DELETE, states the effect is revocation of the secret, and discloses the two guardrails (environment flag and confirm). It omits whether the revocation is irreversible/recoverable and what happens on failure, which keeps it below 5.

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?

Two short sentences, front-loaded with the operation tag and the action, then the preconditions. No filler; every clause (resource, effect, env flag, confirm) is load-bearing.

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 destructive tool with no annotations and no output schema, the definition covers target, effect, and gating requirements. Only the post-condition (what a successful response looks like, and whether the secret is permanently gone) is left unstated.

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 description coverage is 100%, so both `name` (with a full pattern and format) and `confirm` are already fully documented. The description restates the confirm=true requirement but adds no new format or semantics beyond the schema, which is the baseline-3 case.

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?

States a specific verb ("Delete") and a specific resource ("a Measurement Protocol secret"), plus the functional consequence ("revokes it"). The resource is distinct from every listed sibling (create/update measurement protocol secret, account/property/stream deletes), so an agent can select it 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?

Gives concrete preconditions for invocation: GA4_MCP_ENABLE_DELETES=true must be set and confirm=true must be passed. It does not spell out when to choose deletion over disabling/rotating the secret, nor does it name alternatives, so it stops short of full when/when-not 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