Skip to main content
Glama
debanjanbasu

grr

by debanjanbasu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

gmail.users.settings.filters.delete

Permanently deletes a specified Gmail filter for a user, removing it immediately and irreversibly. Use it to clean up unwanted filter rules by providing the user ID and filter ID.

Instructions

Immediately and permanently deletes the specified filter. For more information, see Manage Gmail filters [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.

Input Schema

NameRequiredDescriptionDefault
idYes[URL path segment] The ID of the filter to be deleted.
queryNoExtra KEY=VALUE query pairs for endpoints whose parameters Discovery does not describe.
paramsNoParameter map merged into the request; typed parameters win.
userIdYes[URL path segment] User's email address. The special value "me" can be used to indicate the authenticated user.me
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / id / description
      Previous value: -"The ID of the filter to be deleted."New value: +"[URL path segment] The ID of the filter to be deleted."
    • addedInput schema / properties / userId / default
      Added value: +"me"
    • changedInput schema / properties / userId / description
      Previous value: -"User's email address. The special value \"me\" can be used to indicate the authenticated user."New value: +"[URL path segment] User's email address. The special value \"me\" can be used to indicate the authenticated user."
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the load well: it discloses permanence/irreversibility, the read-only-profile refusal, and the expected return payload. The generic body-construction sentence (typed flags vs `params`, `body_file`) is boilerplate for a DELETE that sends no body and slightly muddies the picture.

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 tight sentences, front-loaded with the destructive action and its irreversibility before the docs link and sibling routing. No wasted preamble.

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?

No output schema exists, and the description fills that gap by stating the post-delete return shape (or empty). Combined with 100% schema coverage and the irreversibility warning, an agent has enough to call it correctly; only explicit preconditions are 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 `userId` (with 'me' default) and `id` are already documented; the description adds nothing specific about them. It only explains the generic precedence of typed flags over `params` and the `body_file` alternative, which is marginal 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+resource ("Immediately and permanently deletes the specified filter") and names the sibling operations on the same resource (create, get, list), so the agent can place it precisely in the Gmail filter toolset.

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?

It identifies the sibling operations but never says when to prefer this over them or what prerequisites (ownership/admin rights, filter existing) apply. The only real routing signal is that it is refused under --readonly profiles, which is a constraint rather than usage 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