Skip to main content
Glama
debanjanbasu

grr

by debanjanbasu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

analyticsadmin.properties.dataStreams.delete

Deletes a DataStream from a Google Analytics property, removing it permanently unless an undo flow exists; use to clean up or retire unused streams.

Instructions

Deletes a DataStream on 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

NameRequiredDescriptionDefault
nameYes[URL path segment] Required. The name of the DataStream to delete. Example format: properties/1234/dataStreams/5678
queryNoExtra KEY=VALUE query pairs for endpoints whose parameters Discovery does not describe.
paramsNoParameter map merged into the request; typed parameters win.
dry_runNoReturn the request that would be sent, without sending it.
body_fileNoRead the request body from this file ('-' for stdin) instead of building one from the parameters.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / name / description
      Previous value: -"Required. The name of the DataStream to delete. Example format: properties/1234/dataStreams/5678"New value: +"[URL path segment] Required. The name of the DataStream to delete. Example format: properties/1234/dataStreams/5678"
    • addedInput schema / properties / name / pattern
      Added value: +"^properties/[^/]+/dataStreams/[^/]+$"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "type": "object"
+}
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

No annotations are provided, and the description carries the full burden well: it discloses irreversibility (with the honest caveat about a possible trash/undo flow), the refusal behavior under read-only safety profiles, and the post-delete return payload. That is substantially more than the name implies.

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 destructive action and its consequences, which is the right ordering for an irreversible tool. The trailing sentence about typed flags vs params map vs body_file is generic boilerplate repeated across the tool family and dilutes the core message slightly.

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?

Output schema exists, so the return shape needs no elaboration, yet the description still notes the post-delete JSON state. Combined with the irreversibility warning and safety-profile refusal, an agent has everything needed to decide and call correctly.

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 coverage is 100% and every parameter already has its own description, including the typed-parameters-win precedence rule and body_file semantics. The description largely restates that resolution order rather than adding format or constraint detail beyond the schema, so baseline 3 applies.

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 DataStream on a property') plus the HTTP method, and explicitly names the sibling set over the same resource (create, get, list, patch). An agent can distinguish it from analyticsadmin.properties.dataStreams.patch or delete without opening either schema.

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?

Clear operating context: irreversible removal, refused under --readonly safety profiles, and the sibling operations listed for contrast. It does not spell out an explicit 'use this when X, use patch when Y' decision rule, so it stops short of full routing guidance.

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