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) }] })

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.0
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observed

TDQS

C2.5/5.0
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. 'Gets a filter' is too minimal; it does not state that the operation is read-only, mention any required permissions, or describe the return value or side effects.

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 short (three words), which is concise but not sufficiently informative. It lacks structure and fails to convey necessary details, making it inadequate despite its brevity.

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?

Even for a simple tool with one parameter and no output schema, the description should specify the type of filter or what the return is. It is incomplete and does not provide enough context for an agent to use it 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?

The input schema covers 100% of parameters, and the description adds no additional meaning beyond the schema's 'id' description. Baseline 3 is appropriate since schema does the work.

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 states the verb 'Gets' and resource 'a filter', which is clear but generic. It does not differentiate from sibling tools like 'get_draft' or 'get_label', so the purpose is only moderately clear.

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?

No guidance is provided on when to use this tool versus alternatives. With siblings like 'list_filters' and 'delete_filter', the description lacks any usage context or prerequisites.

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