Gmail MCP

list_send_as

Retrieve all send-as aliases configured for your Gmail account to view alternative email addresses you can send from.

Instructions

Lists the send-as aliases for the specified account

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_send_as"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Implementation Reference

src/index.ts:1171-1180 (registration)

Tool registration via server.tool() - registers 'list_send_as' with no parameters, lists send-as aliases for the account

server.tool("list_send_as",
  "Lists the send-as aliases for the specified account",
  {},
  async () => {
    return handleTool(config, async (gmail: gmail_v1.Gmail) => {
      const { data } = await gmail.users.settings.sendAs.list({ userId: 'me' })
      return formatResponse(data)
    })
  }
)

src/index.ts:1174-1179 (handler)

Handler function - calls gmail.users.settings.sendAs.list({ userId: 'me' }) and returns formatted response

async () => {
  return handleTool(config, async (gmail: gmail_v1.Gmail) => {
    const { data } = await gmail.users.settings.sendAs.list({ userId: 'me' })
    return formatResponse(data)
  })
}

src/index.ts:1173-1173 (schema)
Empty schema object - no input parameters required for this tool
```
{},
```

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 18, 2025

TDQS

B3.2/5.0

Behavior2/5

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

No annotations provided, so description must carry full burden. It only states the action, lacking details on pagination, ordering, scope requirements, side effects, or behavior for empty results. For a read operation, minimal 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?

Single sentence is concise and front-loaded with key action and resource. No wasted words or redundancy.

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 no output schema and no annotations, the description is too sparse. Missing details on return format, pagination, error conditions, or whether it lists all aliases or active ones. Adequate for a trivial tool but incomplete for an agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema has 0 parameters and description coverage is 100%. Description implicitly conveys that no parameters are needed (account inferred from context). While it doesn't explain why, it is sufficient given the schema.

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?

Description clearly states verb 'Lists' and resource 'send-as aliases' with context 'for the specified account'. However, it does not clarify how the account is specified given the empty input schema (no parameters). Sibling 'get_send_as' suggests listing vs getting, but not explicitly differentiated.

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?

No guidance on when to use this tool versus siblings like 'get_send_as', 'create_send_as', or 'delete_send_as'. Missing context on prerequisites, authorization, or typical use cases.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server