grr

Overview Schema Source Related Servers Discussions Admin

analyticsadmin.properties.keyEvents.delete

Deletes a Key Event from a Google Analytics property by resource name, returning post-delete state and blocking the irreversible removal under read-only safety profiles.

Instructions

Deletes a Key Event [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 Key Event to delete. Format: properties/{property}/keyEvents/{key_event} Example: "properties/123/keyEvents/456"
`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 Key Event to delete. Format: properties/{property}/keyEvents/{key_event} Example: \"properties/123/keyEvents/456\""New value: +"[URL path segment] Required. The resource name of the Key Event to delete. Format: properties/{property}/keyEvents/{key_event} Example: \"properties/123/keyEvents/456\""

addedInput schema / properties / name / pattern

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

changedOutput schema / (root)

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

First observedOct 26, 2026

TDQS

A4/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full burden, and it does substantial work: it warns the effect is irreversible unless a trash/undo flow exists, discloses the readonly-profile refusal, and describes the return payload and body sourcing (typed params win over `params`; `body_file` replaces body construction). It leaves out authorization/permission requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The deletion semantics and irreversibility warning are front-loaded, which is good. But the trailing clause about request bodies being built from typed parameters or `body_file` is largely irrelevant boilerplate for a DELETE with no body, and the single em-dash-chained sentence is denser than needed.

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?

An output schema exists, so return-value explanation is optional, yet the description still says what comes back. Combined with the irreversibility warning, safety-profile constraint, and parameter precedence rule, an agent has enough to invoke this correctly; only permission/auth context is missing.

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 `name`, `query`, `params`, `dry_run`, and `body_file` are already documented in the schema. The description only adds the precedence rule (typed parameters beat the `params` map) and the `body_file` alternative, which is marginal added value over the schema.

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 Key Event'), plus the HTTP method and the semantic effect ('removes the resource'). It then explicitly names the siblings over the same resource (create, get, list, patch), so an agent can route without opening other schemas.

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?

Declares a clear operational constraint — 'refused under --readonly safety profiles' — which is exactly the condition an agent needs before attempting a destructive call. It also enumerates the sibling operations on the same resource, though it never states positively when delete is the right choice versus patch or archive.

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

Deploy Server