grr

Overview Schema Source Related Servers Discussions Admin

analyticsadmin.properties.conversionEvents.patch

Updates a Google Analytics conversion event's attributes via PATCH using a required field mask; deprecated in favor of UpdateKeyEvent.

Instructions

Deprecated: Use UpdateKeyEvent instead. Updates a conversion event with the specified attributes [HTTP PATCH] — updates the resource; refused under --readonly safety profiles. Returns the API's response resource as JSON — request body is a JSON GoogleAnalyticsAdminV1betaConversionEvent object accepting countingMethod, createTime, custom, defaultConversionValue, deletable, eventName, name; pass it via params or whole via body_file Siblings over the same resource: create, delete, get, list.

Input Schema

Name	Required	Description
`name`	Yes	[URL path segment] Identifier. Resource name of this conversion event. Format: properties/{property}/conversionEvents/{conversion_event}
`query`	No	Extra KEY=VALUE query pairs for endpoints whose parameters Discovery does not describe.
`params`	No	Parameter map merged into the request; typed parameters win.
`dry_run`	No	Return the request that would be sent, without sending it.
`body_file`	No	Read the request body from this file ('-' for stdin) instead of building one from the parameters. The body is a JSON GoogleAnalyticsAdminV1betaConversionEvent object.
`updateMask`	No	[query parameter] Required. The list of fields to be updated. Field names must be in snake case (e.g., "field_to_update"). Omitted fields will not be updated. To replace the enti
`request_body`	No	Request body of type GoogleAnalyticsAdminV1betaConversionEvent: pass it via `params` (merged into the built body) or whole via `body_file`.

Output Schema

Name	Required	Description	Default
`name`	No
`custom`	No
`deletable`	No
`eventName`	No
`createTime`	No
`countingMethod`	No
`defaultConversionValue`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 26, 2026

changedInput schema / properties / body_file / description

Previous value: -"Read the request body from this file ('-' for stdin) instead of building one from the parameters."New value: +"Read the request body from this file ('-' for stdin) instead of building one from the parameters. The body is a JSON GoogleAnalyticsAdminV1betaConversionEvent object."

addedInput schema / properties / request_body

Added value: +{
+  "description": "Request body of type GoogleAnalyticsAdminV1betaConversionEvent: pass it via `params` (merged into the built body) or whole via `body_file`.",
+  "properties": {
+    "countingMethod": {
+      "enum": [
+        "CONVERSION_COUNTING_METHOD_UNSPECIFIED",
+        "ONCE_PER_EVENT",
+        "ONCE_PER_SESSION"
+      ],
+      "type": "string"
+    },
+    "createTime": {
+      "type": "string"
+    },
+    "custom": {
+      "type": "boolean"
+    },
+    "defaultConversionValue": {
+      "properties": {
+        "currencyCode": {
+          "type": "string"
+        },
+        "value": {
+          "type": "number"
+        }
+      },
+      "type": "object"
+    },
+    "deletable": {
+      "type": "boolean"
+    },
+    "eventName": {
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed5 schema fields changedOct 26, 2026

changedInput schema / properties / name / description

Previous value: -"Identifier. Resource name of this conversion event. Format: properties/{property}/conversionEvents/{conversion_event}"New value: +"[URL path segment] Identifier. Resource name of this conversion event. Format: properties/{property}/conversionEvents/{conversion_event}"

addedInput schema / properties / name / pattern

Added value: +"^properties/[^/]+/conversionEvents/[^/]+$"

changedInput schema / properties / updateMask / description

Previous value: -"Required. The list of fields to be updated. Field names must be in snake case (e.g., \"field_to_update\"). Omitted fields will not be updated. To replace the enti"New value: +"[query parameter] Required. The list of fields to be updated. Field names must be in snake case (e.g., \"field_to_update\"). Omitted fields will not be updated. To replace the enti"

addedInput schema / properties / updateMask / format
```
Added value: +"google-fieldmask"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "countingMethod": {
+      "enum": [
+        "CONVERSION_COUNTING_METHOD_UNSPECIFIED",
+        "ONCE_PER_EVENT",
+        "ONCE_PER_SESSION"
+      ],
+      "type": "string"
+    },
+    "createTime": {
+      "type": "string"
+    },
+    "custom": {
+      "type": "boolean"
+    },
+    "defaultConversionValue": {
+      "properties": {
+        "currencyCode": {
+          "type": "string"
+        },
+        "value": {
+          "type": "number"
+        }
+      },
+      "type": "object"
+    },
+    "deletable": {
+      "type": "boolean"
+    },
+    "eventName": {
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedOct 26, 2026

TDQS

A4.9/5.0

Behavior5/5

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

With no annotations, the description carries the full burden and does so: it discloses that the operation is a mutation blocked by --readonly profiles, that the response is the API resource as JSON, and how the body can be supplied (params vs body_file). This is exactly the safety and side-effect context the annotations would otherwise provide.

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?

Dense but front-loaded: the deprecation warning and replacement come first, then mechanics. It packs a lot into few sentences, though the trailing sibling enumeration is the least essential clause and could be trimmed without losing guidance.

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

Completeness5/5

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

For a mutating, deprecated tool with an output schema present, the description covers everything an agent needs: deprecation, replacement, read-only refusal, body construction options, and required updateMask semantics are handled by the schema. Nothing material is missing.

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

Parameters5/5

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

Schema coverage is already 100%, so baseline would be 3, but the description adds real value: it enumerates the accepted body fields (countingMethod, createTime, custom, defaultConversionValue, deletable, eventName, name) and explains the two body-passing channels, params and body_file. That clarifies the interplay between the body_file, params, and request_body parameters beyond the schema text.

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 and resource (updates a conversion event), leads with a deprecation notice naming the replacement UpdateKeyEvent, and distinguishes itself from the create/delete/get/list siblings over the same resource. An agent can identify what it does and which tool supersedes 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 Guidelines5/5

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

Explicitly routes the agent away from this tool ("Deprecated: Use UpdateKeyEvent instead") while naming the sibling set for the same resource. It adds the concrete condition that the call is refused under --readonly safety profiles, so an agent knows both the preferred alternative and a hard usage constraint.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server