Skip to main content
Glama

create_forwarding_address

Set up email forwarding in Gmail by specifying a destination address to automatically redirect incoming messages.

Instructions

Creates a forwarding address

Input Schema

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

Implementation Reference

  • The handler function for the 'create_forwarding_address' tool. It uses the shared 'handleTool' helper to manage authentication and executes the Gmail API call to create a new forwarding address.
    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)
      })
    }
  • Input schema for the 'create_forwarding_address' tool, defining the required 'forwardingEmail' parameter using Zod.
    {
      forwardingEmail: z.string().describe("An email address to which messages can be forwarded")
    },
  • src/index.ts:1077-1088 (registration)
    Registration of the 'create_forwarding_address' tool on the MCP server, specifying name, description, input schema, and handler.
    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)
        })
      }
    )
  • Shared 'handleTool' helper function used by all Gmail API tools, including create_forwarding_address. Handles OAuth2 client setup, credential validation, Gmail client creation, API execution, and specialized error handling for authentication issues.
    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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the action ('creates') without detailing outcomes (e.g., whether it returns an ID, requires confirmation, or has side effects), permissions needed, rate limits, or error conditions. This is inadequate 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.

Conciseness3/5

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

The description is a single sentence with no wasted words, but it is under-specified rather than concise. It lacks front-loaded critical information (e.g., purpose differentiation or behavioral traits), making it minimally structured but not effectively brief.

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 mutation tool with no annotations and no output schema, the description is severely incomplete. It fails to explain what happens after creation (e.g., return value or next steps), does not address error handling, and offers no usage context. This leaves 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?

Schema description coverage is 100%, with the single parameter 'forwardingEmail' well-described in the schema. The description adds no additional meaning about the parameter (e.g., format constraints or examples). Baseline 3 is appropriate as the schema handles the documentation burden.

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 restates the tool name without adding specificity. It lacks details about what a forwarding address is, what resource it creates (e.g., in Gmail settings), or how it differs from sibling tools like 'create_send_as' or 'add_delegate'. The purpose is minimally stated but not clarified.

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., needing admin permissions), context (e.g., for email forwarding setup), or exclusions (e.g., not for modifying existing addresses). This leaves the agent with no usage context.

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