Skip to main content
Glama

get_filter

Retrieve a specific Gmail filter configuration by its ID to view or manage email organization rules.

Instructions

Gets a filter

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the filter to be fetched

Implementation Reference

  • src/index.ts:1039-1050 (registration)
    Registration of the 'get_filter' MCP tool, including description, input schema, and inline handler function.
    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)
        })
      }
    )
  • Input schema for the get_filter tool: requires a string 'id' parameter for the filter ID.
    {
      id: z.string().describe("The ID of the filter to be fetched")
    },
  • Handler function for get_filter: authenticates via handleTool, calls Gmail API to get filter by ID, formats and returns 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)
      })
    }
  • Shared helper function handleTool used by get_filter (and all tools) to manage OAuth2 authentication, create Gmail client, execute the API call, and handle errors.
    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}`
      }
    }
  • Helper function formatResponse used to format the API response into MCP content format.
    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 responsibility for behavioral disclosure. 'Gets a filter' implies a read-only operation but doesn't clarify permissions required, error conditions (e.g., invalid ID), response format, or side effects. For a tool with zero annotation coverage, this is insufficient to inform safe or effective use.

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 details (e.g., what a filter is, key constraints) and wastes its limited space on a tautology. Conciseness should not come at the expense of utility.

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 no annotations, no output schema, and a minimal description, this tool definition is incomplete for effective use. The agent lacks context on what a 'filter' entails, how results are structured, error handling, or relation to sibling tools. For a read operation in a complex system (Gmail-like), this leaves significant gaps.

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 has 100% description coverage, with the 'id' parameter clearly documented as 'The ID of the filter to be fetched'. The description adds no additional parameter context beyond this, so it meets the baseline score of 3 where the schema does the heavy lifting. No compensation is needed or provided.

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 meaningful context. It specifies the verb 'gets' and resource 'filter', but fails to distinguish this tool from sibling tools like 'list_filters' or explain what a 'filter' represents in this system (e.g., email filtering rules). This provides minimal value beyond the name itself.

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 doesn't mention sibling tools like 'list_filters' (for listing multiple filters) or 'create_filter' (for creating new ones), nor does it specify prerequisites (e.g., needing a filter ID) or appropriate contexts. This leaves the agent with no usage direction.

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