Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

ga4_create_skadnetwork_conversion_value_schema

Create a SKAdNetwork conversion value schema on a GA4 iOS data stream by supplying postback window settings, enabling SKAdNetwork measurement configuration for app install tracking.

Instructions

[GA4 WRITE] Create the SKAdNetwork conversion value schema on an iOS data stream. Supply postbackWindow settings via body. 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": {
      "property": "<property>",
      "dataStreamId": "<dataStreamId>",
      "confirm": "<confirm>"
    },
    "name": "ga4_create_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.
confirmYesMust be true to apply the change.
propertyYesGA4 property ID, e.g. "123456789" or "properties/123456789".
dataStreamIdYesData stream ID (numeric) or "dataStreams/{id}".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.497.5
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / body / propertyNames
      Added value: +{
      +  "type": "string"
      +}
    • removedInput schema / properties / dataStreamId / minLength
      Removed value: -1
    • addedInput schema / properties / dataStreamId / pattern
      Added value: +"^\\s*(dataStreams\\/)?\\d+\\s*$"
    • removedInput schema / properties / property / minLength
      Removed value: -1
    • addedInput schema / properties / property / pattern
      Added value: +"^\\s*(properties\\/)?\\d+\\s*$"
  2. Addedv1.421.0
  3. Removedv1.350.0
  4. Addedv1.160.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose that this is a gated write operation requiring an environment flag plus confirm=true, which is genuinely useful operational context. It omits what happens if a schema already exists (error vs. overwrite), whether the change is reversible, and rate-limit or permission details.

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 sentences, front-loaded with a clear [GA4 WRITE] marker, then the payload hint and preconditions. No filler; every clause carries information an agent needs before calling.

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 mutation tool with no annotations, no output schema, and a nested free-form body, the definition covers the action, the payload hint, and the write gate. It is still thin on outcome behavior — what is returned, what happens on conflict with an existing schema, and what postbackWindow fields are valid.

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 description coverage is 100%, so baseline is 3, but the description adds real meaning by telling the agent that the free-form `body` parameter must carry postbackWindow settings — information the untyped additionalProperties body schema cannot convey. It still gives no shape or format for those settings.

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 gives a specific verb and resource ('Create the SKAdNetwork conversion value schema on an iOS data stream'), which is far more precise than the tool name alone. It does not explicitly differentiate from the sibling ga4_update_skadnetwork_conversion_value_schema or ga4_delete_skadnetwork_conversion_value_schema, so an agent must infer that this is the create-only path.

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 'Create ... on an iOS data stream', and useful prerequisites are stated (GA4_MCP_ENABLE_WRITES=true, confirm=true). There is no guidance on when to choose create versus update (e.g., whether an existing schema should be updated instead) or when-not to call it.

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