Skip to main content
Glama

delete_send_as

Remove a configured send-as email alias from your Gmail account to manage your sender identity settings.

Instructions

Deletes the specified send-as alias

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sendAsEmailYesThe send-as alias to be deleted

Implementation Reference

  • The handler function that executes the delete_send_as tool. It invokes the Gmail API's users.settings.sendAs.delete method via the shared handleTool wrapper to delete the specified send-as alias.
    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)
      })
    }
  • src/index.ts:1145-1156 (registration)
    Registration of the delete_send_as tool with the MCP server, specifying the tool name, description, input schema, and handler function.
    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)
        })
      }
    )
  • Zod input schema for the delete_send_as tool, defining the required 'sendAsEmail' parameter.
    {
      sendAsEmail: z.string().describe("The send-as alias to be deleted")
    },
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. While 'Deletes' implies a destructive mutation, it doesn't specify whether this action is reversible, what permissions are required, or what happens to associated data. This leaves significant gaps for a destructive operation.

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 directly states the tool's function without unnecessary words. It's front-loaded and wastes no space, making it easy 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?

For a destructive mutation tool with no annotations and no output schema, the description is inadequate. It doesn't explain what happens after deletion, whether there are side effects, or what the return value might be, leaving critical context missing for safe and effective use.

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 'sendAsEmail' fully documented in the schema. The description adds no additional semantic context about the parameter beyond what's in the schema, meeting the baseline for high coverage but not exceeding it.

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 resource ('the specified send-as alias'), making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'remove_delegate' or 'delete_forwarding_address', 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. With sibling tools like 'patch_send_as' and 'update_send_as' available, there's no indication of when deletion is appropriate versus modification, nor any prerequisites or exclusions mentioned.

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