Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

ga4_delete_skadnetwork_conversion_value_schema

Deletes a GA4 SKAdNetwork conversion value schema by full resource name when deletes are enabled and confirm=true.

Instructions

[GA4 DELETE] Delete the SKAdNetwork conversion value schema. 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_skadnetwork_conversion_value_schema"
  }
}

Input Schema

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

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the safety burden. It usefully discloses the two-part gating mechanism (environment flag plus confirm flag) that makes this destructive call fire, but omits irreversibility, whether child resources are affected, and required auth scopes.

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 sentences with the action first and the gating conditions second; every clause carries information. The bracketed '[GA4 DELETE]' prefix is minor redundancy but helps grouping.

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

Completeness3/5

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

For a destructive delete with no annotations and no output schema, the definition covers invocation preconditions adequately but leaves the agent without any statement of consequence or irreversibility. Two fully documented parameters keep the gap from being larger.

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%, so the pattern-constrained resource name and the confirm flag are already fully documented. The description's 'confirm=true' merely restates the schema and adds no new semantics about format or naming.

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?

The description states a specific verb and resource: deleting the SKAdNetwork conversion value schema. The name and description together make the target unambiguous relative to create/update siblings, but the description itself never names those siblings or clarifies scope.

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?

It gives concrete preconditions (GA4_MCP_ENABLE_DELETES=true, confirm=true), which tells the agent when the call will succeed. It does not say when to prefer delete vs. update/reset, nor when deletion is inappropriate, so routing guidance is only implied by the tool 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