Skip to main content
Glama

delete_send_as

Removes a specified send-as alias from your Gmail account to stop using that email address for sending.

Instructions

Deletes the specified send-as alias

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sendAsEmailYesThe send-as alias to be deleted

Implementation Reference

  • src/index.ts:1145-1156 (registration)
    Registration and handler for the 'delete_send_as' tool. It is registered via server.tool(), takes a 'sendAsEmail' string parameter validated with Zod, and delegates to the Gmail API's users.settings.sendAs.delete endpoint.
    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)
        })
      }
    )
  • Input schema for delete_send_as tool: requires a single 'sendAsEmail' string 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. It only states the action but omits behavioral traits like whether deletion is permanent, effects on other settings, or permissions required. This is insufficient for an agent to safely invoke the tool.

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?

The description is a single, front-loaded sentence with no fluff. It is efficient but could benefit from additional context without being overly verbose.

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?

Given the tool's simplicity (one required param, no output schema, no annotations), the description minimally covers the action. However, it lacks completeness regarding side effects and error handling, which are important for a delete operation.

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 parameter 'sendAsEmail' clearly described as 'The send-as alias to be deleted'. The description repeats no param info, so the schema does the work. Baseline score of 3 is appropriate.

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 'Deletes' and the resource 'specified send-as alias', making it immediately obvious what the tool does. It also inherently distinguishes from sibling tools like 'create_send_as' or 'get_send_as'.

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, prerequisites (e.g., alias must exist), or alternatives. Without context, an agent might misuse it or fail to handle error cases.

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