Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

ga4_delete_search_ads_360_link

Deletes a GA4 Search Ads 360 link by full resource name, requiring confirm=true and delete enablement to prevent accidental removal.

Instructions

[GA4 DELETE] Delete a Search Ads 360 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_search_ads_360_link"
  }
}

Input Schema

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

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose two non-obvious traits: a server-side feature flag must be enabled and an explicit confirm=true is required, signalling this is a gated destructive operation; however it says nothing about irreversibility, whether dependent data is detached, or what a failed precondition returns.

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, front-loaded sentences with zero waste: the verb-resource purpose leads and the prerequisites follow. Slightly dense parenthetical gating notation but nothing extraneous.

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 delete with full schema descriptions and no output schema, the definition covers the essentials: what is removed, the identifying resource format (via schema), and the two conditions that must hold. Only the consequences of deletion are left unaddressed.

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%, with patterns and per-parameter descriptions already documenting both fields, so the baseline is 3. The description's mention of confirm=true merely restates the schema and adds no format, naming, or edge-case detail for the resource-name parameter.

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 (Search Ads 360 link), which cleanly separates it from the create/update siblings and from the other link-type deletes (Google Ads, Display & Video 360, AdSense, Firebase). 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 Guidelines3/5

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

The description gives operational preconditions (GA4_MCP_ENABLE_DELETES=true, confirm=true) which help gate invocation, but it never states when to prefer this over an alternative or what a caller should do if the link does not exist. Guidance is implied by the resource name rather than spelled out.

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