grr

Overview Schema Source Related Servers Discussions Admin

analyticsadmin.properties.conversionEvents.delete

Deletes a conversion event from an Analytics property by resource name; this method is deprecated—use DeleteKeyEvent instead, and removal is irreversible.

Instructions

Deprecated: Use DeleteKeyEvent instead. Deletes a conversion event in a property [HTTP DELETE] — removes the resource; irreversible unless the API documents a trash/undo flow; refused under --readonly safety profiles. Returns the post-delete resource state (or empty) as JSON — request bodies are built from the typed parameters (typed flags win over the params map), or read whole from body_file Siblings over the same resource: create, get, list, patch.

Input Schema

Name	Required	Description
`name`	Yes	[URL path segment] Required. The resource name of the conversion event to delete. Format: properties/{property}/conversionEvents/{conversion_event} Example: "properties/123/conver
`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.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 26, 2026

changedInput schema / properties / name / description

Previous value: -"Required. The resource name of the conversion event to delete. Format: properties/{property}/conversionEvents/{conversion_event} Example: \"properties/123/conver"New value: +"[URL path segment] Required. The resource name of the conversion event to delete. Format: properties/{property}/conversionEvents/{conversion_event} Example: \"properties/123/conver"

addedInput schema / properties / name / pattern

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

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "type": "object"
+}

First observedOct 26, 2026

TDQS

A4.1/5.0

Behavior4/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 disclose irreversibility ('irreversible unless a trash/undo flow exists'), refusal under --readonly profiles, and the post-delete return shape. That is meaningful behavioral context most delete tools omit.

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?

Front-loaded with the deprecation notice and the core action, with sibling routing at the end. Dense but nearly every clause earns its place, aside from the somewhat generic request-body mechanics sentence.

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?

Covers purpose, deprecation, safety profile behavior, and return format, and an output schema exists so return values needn't be detailed further. Adequate for an agent to call correctly without opening the schema.

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 description coverage is 100%, so parameter meaning is already documented. The description adds only marginal value by noting that typed parameters win over the params map and that body_file can supply the body; it does not explain the required `name` format beyond what the schema provides.

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 ('Deletes a conversion event in a property') and immediately flags deprecation. It also distinguishes this from its same-resource siblings (create, get, list, patch), so an agent can place it precisely.

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?

Explicitly routes the agent away with 'Deprecated: Use DeleteKeyEvent instead' and names the sibling CRUD operations on the same resource. Clear selection context, though it doesn't spell out the remaining legitimate conditions for using delete at all.

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

Deploy Server