Gmail MCP Server

add_delegate

Grant email access by adding a delegate to manage your Gmail account, enabling shared inbox management and task delegation.

Instructions

Adds a delegate to the specified account

Input Schema

TableJSON Schema

Name	Required	Description	Default
`delegateEmail`	Yes	Email address of delegate to add

Implementation Reference

src/index.ts:967-972 (handler)

The handler function for the 'add_delegate' tool. It invokes the Gmail API to create a new delegate for the user's account using the provided delegate email.

async (params) => {
  return handleTool(config, async (gmail: gmail_v1.Gmail) => {
    const { data } = await gmail.users.settings.delegates.create({ userId: 'me', requestBody: { delegateEmail: params.delegateEmail } })
    return formatResponse(data)
  })
}

src/index.ts:964-966 (schema)
Zod schema defining the input parameters for the 'add_delegate' tool, requiring a delegateEmail string.
```
{
  delegateEmail: z.string().describe("Email address of delegate to add")
},
```

src/index.ts:962-973 (registration)

MCP server tool registration for 'add_delegate', including description, input schema, and handler function.

server.tool("add_delegate",
  "Adds a delegate to the specified account",
  {
    delegateEmail: z.string().describe("Email address of delegate to add")
  },
  async (params) => {
    return handleTool(config, async (gmail: gmail_v1.Gmail) => {
      const { data } = await gmail.users.settings.delegates.create({ userId: 'me', requestBody: { delegateEmail: params.delegateEmail } })
      return formatResponse(data)
    })
  }
)

Schema Changelog

Changes observed during successful MCP inspections.

First observedDec 9, 2025

TDQS

C2.6/5.0

Behavior1/5

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

No annotations are present, and the description fails to disclose any behavioral traits such as side effects, permission requirements, or what happens if the delegate already exists. The description carries the full burden but provides no additional context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, which is concise but too terse to provide necessary context. It could be expanded slightly to improve clarity without losing conciseness.

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 simplicity and lack of output schema or annotations, the description is insufficient. It does not clarify what 'specified account' refers to, nor does it describe the response or error conditions.

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 input schema fully describes the single parameter 'delegateEmail', and the description does not add meaning beyond what the schema provides. With 100% schema coverage, baseline is 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 uses the specific verb 'Adds' and resource 'delegate', clearly indicating the action. It is distinct from siblings like 'remove_delegate' and 'list_delegates', though it does not specify which account is affected.

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 is provided on when to use this tool versus alternatives such as 'remove_delegate' or 'get_delegate'. There is no mention of prerequisites or scenarios where this tool is appropriate.

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

Deploy Server