Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

ga4_update_skadnetwork_conversion_value_schema

Update a GA4 data stream's SKAdNetwork conversion value schema by passing only the fields to change; the update mask is derived automatically. Requires write access and confirmation.

Instructions

[GA4 WRITE] Update the SKAdNetwork conversion value schema. Pass only the fields to change; updateMask is derived from them (override with an explicit updateMask for nested paths). Requires GA4_MCP_ENABLE_WRITES=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_update_skadnetwork_conversion_value_schema"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoRaw request-body object (JSON) merged OVER the typed fields — use for nested/advanced fields not exposed as flat args.
nameYesFull resource name of the SKAdNetwork conversion value schema to target: "properties/{property}/dataStreams/{stream}/sKAdNetworkConversionValueSchema/{id}".
confirmYesMust be true to apply the change.
updateMaskNoComma-separated field paths to update. Omit to derive from the supplied fields.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.497.5
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / body / propertyNames
      Added value: +{
      +  "type": "string"
      +}
    • 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

A4.1/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 reasonably: it labels the tool as a write, declares the environment gate GA4_MCP_ENABLE_WRITES=true, and requires confirm=true before applying. It also clarifies patch-style semantics ('pass only the fields to change') rather than full replacement. It stops short of describing error behavior when the gate is unset or what the response contains.

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?

Three short sentences, front-loaded with the write tag and the resource, then calling rules, then prerequisites. Every sentence adds information and none restates the tool name or schema verbatim.

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 4-parameter mutation tool with no output schema and full parameter documentation, the description covers the essentials an agent needs: write gating, confirm requirement, and mask derivation. Only return-value or failure-mode detail is absent, which is minor here.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema: it explains that updateMask is derived from the supplied fields and that an explicit mask is needed for nested paths — an interaction the schema text only hints at. The raw 'body' merge-over-typed-fields parameter is left to its own schema description.

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 opens with a specific verb+resource: '[GA4 WRITE] Update the SKAdNetwork conversion value schema', which is unambiguous about what is mutated. It does not explicitly contrast itself with the create/delete siblings of the same resource, but the verb alone makes the distinction inferable for an agent.

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 gives concrete calling guidance — pass only the fields to change, let updateMask be derived, and override explicitly for nested paths — plus hard prerequisites (GA4_MCP_ENABLE_WRITES=true and confirm=true). What is missing is any statement of when to prefer this over the create/delete siblings or what happens when the write flag is off.

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