Skip to main content
Glama

get_filter

Retrieve specific Gmail filter details by ID to manage email organization rules and automate message handling in your inbox.

Instructions

Gets a filter

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the filter to be fetched

Implementation Reference

  • src/index.ts:1020-1031 (registration)
    Registration of the 'get_filter' tool on the MCP server, including inline schema definition and handler function that retrieves a specific filter by ID using the Gmail API.
    server.tool("get_filter",
      "Gets a filter",
      {
        id: z.string().describe("The ID of the filter to be fetched")
      },
      async (params) => {
        return handleTool(config, async (gmail: gmail_v1.Gmail) => {
          const { data } = await gmail.users.settings.filters.get({ userId: 'me', id: params.id })
          return formatResponse(data)
        })
      }
    )
  • Handler function for the 'get_filter' tool. It uses the shared handleTool utility to authenticate and call the Gmail API to get the filter by its ID, then formats the response.
    async (params) => {
      return handleTool(config, async (gmail: gmail_v1.Gmail) => {
        const { data } = await gmail.users.settings.filters.get({ userId: 'me', id: params.id })
        return formatResponse(data)
      })
    }
  • Input schema for 'get_filter' tool: requires a string 'id' parameter representing the filter ID.
    {
      id: z.string().describe("The ID of the filter to be fetched")
    },
  • Shared helper function 'handleTool' used by get_filter (and other tools) to handle OAuth2 authentication, client creation, and API call execution with 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 'formatResponse' used by get_filter to format the API response into MCP content structure.
    const formatResponse = (response: any) => ({ content: [{ type: "text", text: JSON.stringify(response) }] })
Behavior1/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'Gets a filter' implies a read-only operation, but it doesn't specify whether this requires authentication, what happens if the filter doesn't exist (e.g., error handling), rate limits, or the format of the returned data. The description lacks any behavioral context beyond the basic verb.

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

Conciseness2/5

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

While concise with only two words, the description is under-specified rather than efficiently informative. It lacks front-loaded critical information and fails to earn its place by adding value beyond the tool name. True conciseness balances brevity with completeness, which this does not achieve.

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

Completeness1/5

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

Given no annotations, no output schema, and a minimal description, this is completely inadequate for a tool that presumably retrieves a specific resource. The description doesn't explain what a 'filter' is in this context, what data is returned, or any behavioral expectations. Sibling tools suggest this is part of an email/Gmail system, but the description provides no such contextual clues.

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' clearly documented in the schema as 'The ID of the filter to be fetched'. The description adds no additional parameter information beyond what the schema provides, so it meets the baseline score of 3 for adequate coverage when the schema does the heavy lifting.

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 'Gets a filter' is a tautology that merely restates the tool name without adding specificity. It doesn't clarify what type of filter is being retrieved (e.g., email filter, data filter) or what resource it operates on, though sibling tools suggest this is likely related to email/Gmail filters. The description fails to distinguish this tool from similar siblings like 'list_filters' or 'create_filter'.

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. There's no mention of prerequisites (e.g., needing a filter ID), comparison to sibling tools like 'list_filters' for browsing all filters, or context about when fetching a specific filter is appropriate versus creating or listing filters.

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