Skip to main content
Glama

create_forwarding_address

Set up email forwarding in Gmail by creating a forwarding address to automatically redirect incoming messages to another email account.

Instructions

Creates a forwarding address

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
forwardingEmailYesAn email address to which messages can be forwarded

Implementation Reference

  • src/index.ts:1044-1055 (registration)
    Registration of the create_forwarding_address tool on the MCP server, including schema and inline handler implementation.
    server.tool("create_forwarding_address",
      "Creates a forwarding address",
      {
        forwardingEmail: z.string().describe("An email address to which messages can be forwarded")
      },
      async (params) => {
        return handleTool(config, async (gmail: gmail_v1.Gmail) => {
          const { data } = await gmail.users.settings.forwardingAddresses.create({ userId: 'me', requestBody: params })
          return formatResponse(data)
        })
      }
    )
  • Handler executes the tool logic by calling Gmail API's users.settings.forwardingAddresses.create via the shared handleTool wrapper.
    async (params) => {
      return handleTool(config, async (gmail: gmail_v1.Gmail) => {
        const { data } = await gmail.users.settings.forwardingAddresses.create({ userId: 'me', requestBody: params })
        return formatResponse(data)
      })
    }
  • Zod schema defining the input parameter forwardingEmail.
    {
      forwardingEmail: z.string().describe("An email address to which messages can be forwarded")
    },
  • Shared helper function handleTool that sets up OAuth2 client, validates credentials, creates Gmail client, and executes the 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}`
      }
    }
  • Helper function to format API responses for MCP tool output.
    const formatResponse = (response: any) => ({ content: [{ type: "text", text: JSON.stringify(response) }] })
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It states a write operation ('Creates') but fails to describe traits like required permissions, rate limits, side effects (e.g., email forwarding activation), or response format. This leaves critical behavioral aspects undocumented for a mutation tool.

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

Conciseness5/5

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

The description is extremely concise with a single sentence, 'Creates a forwarding address', which is front-loaded and wastes no words. However, this conciseness comes at the cost of under-specification, but it earns full points for brevity and structure.

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 as a write operation with no annotations and no output schema, the description is incomplete. It lacks details on behavior, usage, or expected outcomes, failing to provide adequate context for an agent to invoke it correctly in a server with many sibling tools.

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 'forwardingEmail' well-documented in the schema. The description adds no parameter semantics beyond what the schema provides, so it meets the baseline of 3 without compensating for gaps, as there are none.

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 forwarding address' is a tautology that merely restates the tool name without adding specificity or distinguishing it from siblings. It lacks details about what resource is being created (e.g., in Gmail settings) or how it functions, making it vague compared to tools like 'create_filter' or 'create_label'.

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention prerequisites (e.g., user permissions), context (e.g., setting up email forwarding), or exclusions, leaving the agent with no usage direction among siblings like 'update_auto_forwarding' or 'get_forwarding_address'.

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