Skip to main content
Glama

delete_send_as

Remove a configured send-as email alias from your Gmail account to manage sending identities.

Instructions

Deletes the specified send-as alias

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sendAsEmailYesThe send-as alias to be deleted

Implementation Reference

  • src/index.ts:1112-1123 (registration)
    Registration of the 'delete_send_as' MCP tool, including description, input schema, and handler function that deletes a send-as alias via Gmail API.
    server.tool("delete_send_as",
      "Deletes the specified send-as alias",
      {
        sendAsEmail: z.string().describe("The send-as alias to be deleted")
      },
      async (params) => {
        return handleTool(config, async (gmail: gmail_v1.Gmail) => {
          const { data } = await gmail.users.settings.sendAs.delete({ userId: 'me', sendAsEmail: params.sendAsEmail })
          return formatResponse(data)
        })
      }
    )
  • Handler function executing the 'delete_send_as' tool logic: authenticates via handleTool, calls Gmail API to delete the sendAsEmail alias, and formats response.
    async (params) => {
      return handleTool(config, async (gmail: gmail_v1.Gmail) => {
        const { data } = await gmail.users.settings.sendAs.delete({ userId: 'me', sendAsEmail: params.sendAsEmail })
        return formatResponse(data)
      })
    }
  • Zod input schema for 'delete_send_as' tool: requires 'sendAsEmail' as string.
    {
      sendAsEmail: z.string().describe("The send-as alias to be deleted")
    },
  • Shared 'handleTool' helper used by 'delete_send_as' (and other tools) for OAuth2 client creation, credential validation, Gmail client setup, API call execution, and error handling.
    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}`
      }
    }
  • Shared 'formatResponse' helper used to format tool responses as MCP content blocks with JSON stringified data.
    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 provided, the description carries the full burden of behavioral disclosure. It states the action is a deletion, implying a destructive mutation, but doesn't specify whether this is permanent, reversible, requires specific permissions, or has side effects (e.g., impact on sent emails). For a destructive tool with zero annotation coverage, this is a significant gap in transparency.

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 front-loads the core action ('Deletes') and resource ('send-as alias') without any unnecessary words. It earns its place by clearly stating the tool's purpose in minimal space, making it easy for an agent to parse quickly.

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 destructive nature (implied by 'Deletes'), lack of annotations, and no output schema, the description is incomplete. It doesn't cover behavioral aspects like irreversibility, permission requirements, error conditions, or what happens post-deletion. For a mutation tool with no structured safety hints, more context is needed to guide safe usage.

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 description mentions 'the specified send-as alias', which aligns with the single parameter 'sendAsEmail' in the input schema. Since schema description coverage is 100% (the parameter is fully documented as 'The send-as alias to be deleted'), the description adds no additional semantic value beyond what the schema provides, meeting the baseline score of 3.

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 ('Deletes') and the target resource ('the specified send-as alias'), making the purpose immediately understandable. It distinguishes from siblings like 'delete_message' or 'delete_label' by specifying the exact resource type, though it doesn't explicitly contrast with similar tools like 'remove_delegate' or 'delete_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 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. It doesn't mention prerequisites (e.g., needing an existing send-as alias), exclusions, or related tools like 'create_send_as', 'patch_send_as', 'update_send_as', 'get_send_as', 'list_send_as', or 'verify_send_as' from the sibling list, leaving the agent to infer 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/HitmanLy007/gmail-mcp'

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