Skip to main content
Glama

create_filter

Create Gmail filters to automatically organize emails by applying labels, forwarding messages, or removing labels based on sender, subject, attachments, or search criteria.

Instructions

Creates a filter

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
criteriaYesFilter criteria
actionYesActions to perform on messages matching the criteria

Implementation Reference

  • The handler function that executes the create_filter tool logic. It invokes handleTool to authenticate and call the Gmail API's users.settings.filters.create method with the provided parameters, then formats the response.
    async (params) => {
      return handleTool(config, async (gmail: gmail_v1.Gmail) => {
        const { data } = await gmail.users.settings.filters.create({ userId: 'me', requestBody: params })
        return formatResponse(data)
      })
    }
  • Zod schema for input validation of the create_filter tool, defining criteria for matching emails and actions to apply (add/remove labels or forward).
      criteria: z.object({
        from: z.string().optional().describe("The sender's display name or email address"),
        to: z.string().optional().describe("The recipient's display name or email address"),
        subject: z.string().optional().describe("Case-insensitive phrase in the message's subject"),
        query: z.string().optional().describe("A Gmail search query that specifies the filter's criteria"),
        negatedQuery: z.string().optional().describe("A Gmail search query that specifies criteria the message must not match"),
        hasAttachment: z.boolean().optional().describe("Whether the message has any attachment"),
        excludeChats: z.boolean().optional().describe("Whether the response should exclude chats"),
        size: z.number().optional().describe("The size of the entire RFC822 message in bytes"),
        sizeComparison: z.enum(['smaller', 'larger']).optional().describe("How the message size in bytes should be in relation to the size field")
      }).describe("Filter criteria"),
      action: z.object({
        addLabelIds: z.array(z.string()).optional().describe("List of labels to add to messages"),
        removeLabelIds: z.array(z.string()).optional().describe("List of labels to remove from messages"),
        forward: z.string().optional().describe("Email address that the message should be forwarded to")
      }).describe("Actions to perform on messages matching the criteria")
    },
  • src/index.ts:1012-1039 (registration)
    The MCP server.tool registration for the create_filter tool, specifying the tool name, description, input schema, and handler function.
    server.tool("create_filter",
      "Creates a filter",
      {
        criteria: z.object({
          from: z.string().optional().describe("The sender's display name or email address"),
          to: z.string().optional().describe("The recipient's display name or email address"),
          subject: z.string().optional().describe("Case-insensitive phrase in the message's subject"),
          query: z.string().optional().describe("A Gmail search query that specifies the filter's criteria"),
          negatedQuery: z.string().optional().describe("A Gmail search query that specifies criteria the message must not match"),
          hasAttachment: z.boolean().optional().describe("Whether the message has any attachment"),
          excludeChats: z.boolean().optional().describe("Whether the response should exclude chats"),
          size: z.number().optional().describe("The size of the entire RFC822 message in bytes"),
          sizeComparison: z.enum(['smaller', 'larger']).optional().describe("How the message size in bytes should be in relation to the size field")
        }).describe("Filter criteria"),
        action: z.object({
          addLabelIds: z.array(z.string()).optional().describe("List of labels to add to messages"),
          removeLabelIds: z.array(z.string()).optional().describe("List of labels to remove from messages"),
          forward: z.string().optional().describe("Email address that the message should be forwarded to")
        }).describe("Actions to perform on messages matching the criteria")
      },
      async (params) => {
        return handleTool(config, async (gmail: gmail_v1.Gmail) => {
          const { data } = await gmail.users.settings.filters.create({ userId: 'me', requestBody: params })
          return formatResponse(data)
        })
      }
    )
  • Shared helper function handleTool used by create_filter (and other tools) to handle OAuth2 authentication, Gmail client creation, API call execution, and error handling including auth-specific 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) {
        // Check for specific authentication errors
        if (
          error.message?.includes("invalid_grant") ||
          error.message?.includes("refresh_token") ||
          error.message?.includes("invalid_client") ||
          error.message?.includes("unauthorized_client") ||
          error.code === 401 ||
          error.code === 403
        ) {
          return formatResponse({
            error: `Authentication failed: ${error.message}. Please re-authenticate by running: npx @shinzolabs/gmail-mcp auth`,
          });
        }
    
        return formatResponse({ error: `Tool execution failed: ${error.message}` });
      }
    }
Behavior1/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 but offers none. It doesn't indicate whether this is a read or write operation, what permissions are required, whether it's idempotent, or what happens on success/failure. For a tool that creates resources, this lack of transparency is critical.

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 technically concise with two words, this is under-specification rather than effective brevity. The description fails to provide necessary context and doesn't front-load essential information, making it inefficient despite its short length.

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?

For a tool that creates resources with complex nested parameters and no output schema, the description is completely inadequate. It doesn't explain what a filter is, what system it operates in, what happens after creation, or provide any behavioral context, leaving significant gaps for agent understanding.

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, thoroughly documenting both 'criteria' and 'action' parameters with their nested properties. The description adds no additional parameter information beyond the schema, so it meets the baseline of 3 where 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 'Creates a filter' is a tautology that restates the tool name without providing meaningful context. It doesn't specify what type of filter (e.g., email filter in Gmail) or what resources it operates on, making it vague compared to more specific sibling tools like 'create_label' or 'create_forwarding_address'.

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 prerequisites, related tools like 'list_filters' or 'delete_filter', or typical use cases, leaving the agent with no context for appropriate invocation.

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

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