Skip to main content
Glama

add_delegate

Grant access to your Gmail account by adding a delegate who can manage emails and settings on your behalf.

Instructions

Adds a delegate to the specified account

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
delegateEmailYesEmail address of delegate to add

Implementation Reference

  • src/index.ts:948-959 (registration)
    Registration of the 'add_delegate' MCP tool, including description, input schema, and inline handler function that uses the Gmail API to add a delegate.
    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)
        })
      }
    )
  • Handler function executing the 'add_delegate' tool logic: authenticates via handleTool and calls Gmail API to create a delegate with the provided 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)
      })
    }
  • Input schema for 'add_delegate' tool using Zod: requires delegateEmail as string.
    {
      delegateEmail: z.string().describe("Email address of delegate to add")
    },
  • Generic helper function 'handleTool' used by all tools including 'add_delegate' for OAuth2 authentication and Gmail client creation before executing the API call.
    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 'formatResponse' used to format API responses for all tools including 'add_delegate' into MCP content format.
    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?

With no annotations provided, the description carries full burden for behavioral disclosure. It states the tool performs an addition operation but doesn't disclose important traits: whether this requires specific permissions, if delegates have limited vs full access, whether the operation is reversible (hinting at 'remove_delegate'), rate limits, or what happens on success/failure. For a mutation tool with zero annotation coverage, this leaves significant 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 with zero wasted words. It's appropriately sized for a simple tool with one parameter and gets straight to the point without unnecessary elaboration.

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?

For a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what 'delegate' means in this context, what permissions delegates receive, whether there are limits on delegate counts, or what the tool returns. Given the complexity of account delegation and the lack of structured data, the description should provide more contextual information.

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 single parameter 'delegateEmail' fully documented in the schema. The description adds no parameter-specific information beyond what's already in the schema (it doesn't explain email format requirements, domain restrictions, or validation rules). Baseline 3 is appropriate when the schema does the heavy lifting.

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 action ('Adds') and resource ('delegate to the specified account'), providing a specific verb+resource combination. It distinguishes from sibling tools like 'remove_delegate' and 'list_delegates' by specifying the add operation, though it doesn't explicitly differentiate from other account modification tools like 'update_auto_forwarding'.

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 admin permissions), when delegation is appropriate, or how this differs from similar tools like 'create_forwarding_address' or 'update_auto_forwarding' that also manage account access. The agent must infer usage from the tool 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