Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

ga4_delete_adsense_link

Deletes a GA4 AdSense link using its full resource name, requiring confirm=true and GA4 delete enablement.

Instructions

[GA4 DELETE] Delete an AdSense link. 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_adsense_link"
  }
}

Input Schema

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

TDQS

A4/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 full burden and does disclose the important operational facts: this is a delete, it is gated behind an environment flag, and it requires an explicit confirm=true. It stops short of stating that the deletion is irreversible or what happens on a missing/invalid link, which are the remaining behaviors an agent would want.

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, zero filler, with the action stated first and the prerequisites immediately after. Every clause carries information the agent needs.

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 destructive, no-annotation, no-output-schema tool, the definition covers the target, the confirmation requirement, and the server-side enablement gate — enough to call it correctly. It could be stronger with a note on irreversibility or error conditions, but nothing essential is missing.

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%: the name parameter is documented with a format and regex, and confirm is documented as "Must be true to delete." The description only echoes confirm=true and adds the non-parameter env-var gate, so it adds little semantic meaning beyond the schema baseline.

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 states a specific verb and resource ("Delete an AdSense link") and the [GA4 DELETE] prefix plus the resource name make it trivially distinguishable from the many sibling delete tools (firebase link, google ads link, etc.) and from ga4_create_adsense_link. No schema opening is required to know what it does.

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

Usage Guidelines3/5

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

Usage is implied by the explicit delete verb and by the two gating conditions (GA4_MCP_ENABLE_DELETES=true, confirm=true), which tell the agent when the call will succeed. However, no alternative or when-not guidance is given, and nothing tells the agent to prefer a disable/update path or how to discover the target link name.

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