Skip to main content
Glama

delete_filter

Remove unwanted email filters from your Gmail account by specifying the filter ID to delete. This tool helps manage your inbox organization by eliminating outdated or unnecessary filtering rules.

Instructions

Deletes a filter

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the filter to be deleted

Implementation Reference

  • src/index.ts:1026-1037 (registration)
    Registration of the 'delete_filter' MCP tool. Includes input schema (filter ID), description, and inline handler function that uses handleTool to authenticate and call Gmail API to delete the specified filter.
    server.tool("delete_filter",
      "Deletes a filter",
      {
        id: z.string().describe("The ID of the filter to be deleted")
      },
      async (params) => {
        return handleTool(config, async (gmail: gmail_v1.Gmail) => {
          const { data } = await gmail.users.settings.filters.delete({ userId: 'me', id: params.id })
          return formatResponse(data)
        })
      }
    )
  • Handler function for delete_filter tool. Takes params, uses shared handleTool to validate OAuth2 credentials, create Gmail client, delete filter by ID via Gmail API, and format response.
      async (params) => {
        return handleTool(config, async (gmail: gmail_v1.Gmail) => {
          const { data } = await gmail.users.settings.filters.delete({ userId: 'me', id: params.id })
          return formatResponse(data)
        })
      }
    )
  • Input schema for delete_filter tool using Zod: requires 'id' string (Gmail filter ID).
      id: z.string().describe("The ID of the filter to be deleted")
    },
  • Shared helper function handleTool used by delete_filter and other tools for OAuth2 authentication, Gmail client creation, API call execution, and error handling.
    const handleTool = async (queryConfig: Record<string, any> | undefined, apiCall: (gmail: gmail_v1.Gmail) => Promise<any>) => {
      try {
        const oauth2Client = queryConfig ? createOAuth2Client(queryConfig) : defaultOAuth2Client
        if (!oauth2Client) throw new Error('OAuth2 client could not be created, please check your credentials')
    
        const credentialsAreValid = await validateCredentials(oauth2Client)
        if (!credentialsAreValid) throw new Error('OAuth2 credentials are invalid, please re-authenticate')
    
        const gmailClient = queryConfig ? google.gmail({ version: 'v1', auth: oauth2Client }) : defaultGmailClient
        if (!gmailClient) throw new Error('Gmail client could not be created, please check your credentials')
    
        const result = await apiCall(gmailClient)
        return result
      } catch (error: any) {
        return `Tool execution failed: ${error.message}`
      }
    }
  • Shared helper to format API responses as MCP content blocks with JSON stringified data.
    const formatResponse = (response: any) => ({ content: [{ type: "text", text: JSON.stringify(response) }] })
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Deletes a filter' implies a destructive mutation, but doesn't specify whether deletion is permanent or reversible, what permissions are required, whether it affects associated data, or what happens on success/failure. For a destructive operation with zero annotation coverage, this leaves critical behavioral traits undocumented.

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?

The description is maximally concise at two words ('Deletes a filter'), with zero wasted text. It's front-loaded with the core action and resource. Every word earns its place, though this conciseness comes at the expense of completeness for other dimensions.

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

Completeness2/5

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

Given this is a destructive mutation tool with no annotations, no output schema, and minimal description, the description is incomplete. It doesn't address what happens after deletion, error conditions, or behavioral implications. For a tool that permanently removes data, more context about consequences and requirements would be expected.

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%, with the single parameter 'id' fully documented in the schema as 'The ID of the filter to be deleted'. The description adds no additional parameter context beyond what the schema provides. According to guidelines, when schema coverage is high (>80%), the baseline score is 3 even with no parameter info in the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Deletes a filter' clearly states the action (delete) and resource (filter), providing basic purpose. However, it doesn't differentiate from sibling tools like delete_draft, delete_label, or delete_message, which all follow the same 'delete [resource]' pattern. The purpose is clear but lacks specificity about what distinguishes this particular deletion operation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. There's no mention of prerequisites (e.g., needing an existing filter ID), when deletion is appropriate versus modification, or how this differs from related tools like delete_filter versus create_filter or list_filters. The agent must infer usage from the name alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nk900600/gmail-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server