Skip to main content
Glama

get_send_as

Retrieve a specific send-as alias configuration from Gmail to verify or use alternative sender identities for email management.

Instructions

Gets the specified send-as alias

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sendAsEmailYesThe send-as alias to be retrieved

Implementation Reference

  • src/index.ts:1144-1155 (registration)
    Registration of the 'get_send_as' MCP tool, including input schema, description, and handler function that calls the Gmail API to retrieve a specific send-as alias.
    server.tool("get_send_as",
      "Gets the specified send-as alias",
      {
        sendAsEmail: z.string().describe("The send-as alias to be retrieved")
      },
      async (params) => {
        return handleTool(config, async (gmail: gmail_v1.Gmail) => {
          const { data } = await gmail.users.settings.sendAs.get({ userId: 'me', sendAsEmail: params.sendAsEmail })
          return formatResponse(data)
        })
      }
    )
  • The handler function for the 'get_send_as' tool. It uses the shared handleTool helper to authenticate, create a Gmail client, call users.settings.sendAs.get with the provided sendAsEmail, and format the response.
    async (params) => {
      return handleTool(config, async (gmail: gmail_v1.Gmail) => {
        const { data } = await gmail.users.settings.sendAs.get({ userId: 'me', sendAsEmail: params.sendAsEmail })
        return formatResponse(data)
      })
    }
  • Input schema for the 'get_send_as' tool, requiring a single string parameter 'sendAsEmail'.
    {
      sendAsEmail: z.string().describe("The send-as alias to be retrieved")
    },
  • Shared helper function used by all tools, including 'get_send_as', to handle OAuth2 authentication, Gmail client creation, 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}`
      }
    }
  • Helper function 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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states a read operation ('gets'), implying it's non-destructive, but doesn't cover error conditions (e.g., if the alias doesn't exist), authentication needs, rate limits, or return format. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 ('gets') and resource ('send-as alias'). There is no wasted verbiage or redundancy, 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?

Given no annotations, no output schema, and a simple parameter schema, the description is incomplete. It lacks behavioral details (e.g., error handling), usage context, and output expectations. For a retrieval tool in a complex email system, more guidance is needed to ensure correct agent invocation.

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' fully documented in the schema as 'The send-as alias to be retrieved'. The description adds no additional meaning beyond this, such as format examples or constraints. Given the high schema coverage, the baseline score of 3 is appropriate.

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 verb ('gets') and resource ('specified send-as alias'), making the purpose immediately understandable. It distinguishes from siblings like 'list_send_as' (which retrieves multiple) and 'create_send_as'/'update_send_as' (which modify). However, it doesn't explicitly mention that this retrieves a single alias by identifier, which would make it fully specific.

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 alias), contrast with 'list_send_as' for multiple aliases, or specify use cases like verifying alias details. Without such context, the agent must infer usage from the name alone.

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

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