Skip to main content
Glama

update_auto_forwarding

Configure automatic email forwarding in Gmail by setting forwarding address, enabling/disabling the feature, and specifying what happens to original messages after forwarding.

Instructions

Updates automatic forwarding settings

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
enabledYesWhether all incoming mail is automatically forwarded to another address
emailAddressYesEmail address to which messages should be automatically forwarded
dispositionYesThe state in which messages should be left after being forwarded

Implementation Reference

  • Shared helper function that handles OAuth2 authentication, client creation, and executes the Gmail API call provided by the tool handler.
        const oauth2Client = new OAuth2Client({
          clientId: credentials?.clientId,
          clientSecret: credentials?.clientSecret,
          redirectUri: `http://localhost:${AUTH_SERVER_PORT}/oauth2callback`
        })
    
        if (credentials?.refreshToken) oauth2Client.setCredentials({ refresh_token: credentials.refreshToken })
    
        return oauth2Client
      } catch (error: any) {
        return null
      }
    }
    
    export const launchAuthServer = async (oauth2Client: OAuth2Client) => new Promise((resolve, reject) => {
      const server = http.createServer()
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Updates' implies a mutation operation, but the description doesn't disclose whether this requires specific permissions, whether changes are immediate or reversible, what happens to existing settings not mentioned, or any rate limits. This is a significant gap for a mutation tool with zero annotation coverage.

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 a single, efficient sentence that states the core purpose without any wasted words. It's appropriately sized for a straightforward update operation and is front-loaded with the essential information.

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?

For a mutation tool with no annotations and no output schema, the description is inadequate. It doesn't explain what the tool returns (success/failure, updated settings), doesn't mention authentication requirements or side effects, and provides no behavioral context. The 100% schema coverage helps with parameters but doesn't compensate for the lack of operational guidance.

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%, so the schema already fully documents all three parameters (enabled, emailAddress, disposition) with clear descriptions and an enum for disposition. The description adds no additional parameter information beyond what's in the schema, meeting the baseline for high schema coverage.

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

Purpose4/5

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

The description clearly states the action ('Updates') and the target resource ('automatic forwarding settings'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its sibling 'get_auto_forwarding' or other settings update tools like 'update_vacation' or 'update_imap', which prevents a perfect score.

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 versus alternatives. There's no mention of prerequisites (e.g., needing existing forwarding settings), when not to use it, or how it differs from related tools like 'create_forwarding_address' or 'update_vacation'.

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