Gmail MCP

Overview Schema Source Related Servers Discussions Admin

get_delegate

Retrieve a specific delegate's information from your Gmail account to manage email access permissions and delegation settings.

Instructions

Gets the specified delegate

Input Schema

TableJSON Schema

Name	Required	Description	Default
`delegateEmail`	Yes	The email address of the delegate to retrieve

Implementation Reference

src/index.ts:955-966 (handler)

Registration and inline handler for the 'get_delegate' tool. The handler authenticates via handleTool, calls the Gmail API to retrieve the specified delegate, and formats the response.

server.tool("get_delegate",
  "Gets the specified delegate",
  {
    delegateEmail: z.string().describe("The email address of the delegate to retrieve")
  },
  async (params) => {
    return handleTool(config, async (gmail: gmail_v1.Gmail) => {
      const { data } = await gmail.users.settings.delegates.get({ userId: 'me', delegateEmail: params.delegateEmail })
      return formatResponse(data)
    })
  }
)

src/index.ts:957-959 (schema)
Input schema for the get_delegate tool, defining the required 'delegateEmail' parameter.
```
{
  delegateEmail: z.string().describe("The email address of the delegate to retrieve")
},
```

src/index.ts:49-65 (helper)

Shared helper function 'handleTool' used by get_delegate (and all tools) for OAuth2 authentication, credential validation, Gmail client creation, 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}`
  }
}

src/index.ts:47-47 (helper)
Helper function 'formatResponse' used to format the API response into MCP content format.
```
const formatResponse = (response: any) => ({ content: [{ type: "text", text: JSON.stringify(response) }] })
```

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.0.0Jan 4, 2026
- addedInput schema / $schema
```
Added value: +"http://json-schema.org/draft-07/schema#"
```
- addedInput schema / additionalProperties
```
Added value: +false
```
First observedNov 18, 2025

TDQS

A3.7/5.0

Behavior3/5

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

The description implies a read-only operation ('Gets'), but without annotations, it does not explicitly state behavioral traits like idempotency, auth requirements, or side effects. It is minimally adequate but not rich.

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?

Extremely concise single sentence with no wasted words. Front-loads the action and resource efficiently.

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?

For a simple get operation with one parameter and no output schema, the description does not specify what is returned. It is adequate but could be more complete by hinting at the return value or structure.

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 coverage is 100% with a clear parameter description in the schema. The tool description adds no extra meaning beyond what the schema already provides, so baseline 3.

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 ('Gets') and the resource ('the specified delegate'), distinguishing it from siblings like list_delegates (list all) and remove_delegate (delete).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use or when not to use. The purpose is implied by the parameter (delegateEmail) and sibling context, but the description lacks explicit alternatives or exclusions.

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

Deploy Server