Skip to main content
Glama

create_forwarding_address

Set up email forwarding by creating a forwarding address that redirects 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:1077-1088 (registration)
    The tool 'create_forwarding_address' is registered via server.tool() with a description 'Creates a forwarding address', a single string parameter 'forwardingEmail', and an inline async handler that calls gmail.users.settings.forwardingAddresses.create.
    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)
        })
      }
    )
  • The handler function for 'create_forwarding_address' invokes the Gmail API's forwardingAddresses.create method with the userId 'me' and the request body containing the forwardingEmail parameter, then wraps the result using formatResponse.
    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)
      })
    }
  • The input schema for 'create_forwarding_address' is a Zod object with a required 'forwardingEmail' parameter (z.string()), which represents the email address to which messages can be forwarded.
    {
      forwardingEmail: z.string().describe("An email address to which messages can be forwarded")
    },
Behavior2/5

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

No annotations exist, and the description only says 'Creates', implying mutation but not disclosing behavioral traits such as whether it triggers a verification email, duplicates handling, or return value.

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

Conciseness4/5

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

One sentence, front-loaded, with no wasted words; however, it could be more informative without being longer.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple create tool with one parameter and no output schema, the description is sufficient for basic understanding but lacks context on side effects or related processes like verification.

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 coverage is 100%, so the schema already describes the single parameter; the description adds no additional meaning beyond the verb.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action 'Creates' and the resource 'forwarding address', which distinguishes it from siblings like 'delete_forwarding_address' and 'list_forwarding_addresses'.

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?

The description provides no guidance on when to use this tool vs alternatives, or any prerequisites like authentication or existing address verification.

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

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