Skip to main content
Glama

delete_filter

Remove unwanted email filters from your Gmail account by specifying the filter ID to maintain organized inbox management.

Instructions

Deletes a filter

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the filter to be deleted

Implementation Reference

  • src/index.ts:1007-1018 (registration)
    Registration of the 'delete_filter' tool, including inline schema and handler. The handler authenticates via handleTool and calls Gmail API to delete the filter by ID.
    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)
        })
      }
    )
  • Core handler logic for delete_filter: calls Gmail users.settings.filters.delete with the provided filter ID after authentication.
    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)
      })
    }
  • Zod input schema defining the required 'id' parameter as a string.
    {
      id: z.string().describe("The ID of the filter to be deleted")
    },
  • Shared helper function used by delete_filter (and other tools) for OAuth2 authentication, client creation, and executing the Gmail API call.
    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}`
      }
    }
Behavior1/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 of behavioral disclosure. 'Deletes a filter' indicates a destructive mutation, but it does not specify whether deletion is permanent, reversible, requires specific permissions, or has side effects (e.g., impacting associated messages). It lacks details on error handling, rate limits, or response format, leaving 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.

Conciseness3/5

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

The description is extremely concise ('Deletes a filter'), which is efficient but under-specified. It is front-loaded with the core action, but the brevity sacrifices necessary context for a mutation tool. While not verbose, it lacks the detail needed for effective use, making it more sparse than optimally concise.

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 the tool's complexity (a destructive delete operation), lack of annotations, and no output schema, the description is incomplete. It does not address behavioral aspects like permanence, permissions, or error cases, nor does it explain return values or side effects. For a mutation tool with no structured support, this minimal description is inadequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 1 parameter with 100% description coverage ('The ID of the filter to be deleted'), so the schema fully documents the parameter. The description adds no parameter semantics beyond this, but with 0 parameters needing compensation and high schema coverage, the baseline is 4. No value is added, but no gap exists.

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

Purpose2/5

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

The description 'Deletes a filter' restates the tool name 'delete_filter' almost verbatim, making it tautological. It specifies the verb 'deletes' and resource 'filter', but fails to distinguish it from sibling tools like 'delete_draft' or 'delete_label' beyond the resource name. No additional context about what a filter is or its scope is provided.

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

Usage Guidelines1/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. It does not mention prerequisites (e.g., needing an existing filter ID), exclusions, or related tools like 'create_filter' or 'list_filters' from the sibling list. Usage is implied only by the name, with no explicit instructions.

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/HitmanLy007/gmail-mcp'

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