Skip to main content
Glama

add_delegate

Add a delegate to your Gmail account to grant access for managing emails and settings. Simplify delegation with this direct tool.

Instructions

Adds a delegate to the specified account

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
delegateEmailYesEmail address of delegate to add

Implementation Reference

  • src/index.ts:962-973 (registration)
    Registration and handler for the add_delegate tool. Registers the tool with name 'add_delegate', takes a delegateEmail string parameter via Zod schema, and the handler calls the Gmail API's users.settings.delegates.create endpoint.
    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)
        })
      }
    )
  • Zod schema for add_delegate tool input. Defines a single required parameter 'delegateEmail' (string) describing the email address of the delegate to add.
    {
      delegateEmail: z.string().describe("Email address of delegate to add")
    },
  • Handler function for add_delegate. Uses handleTool to validate OAuth, then calls gmail.users.settings.delegates.create with the delegateEmail parameter and returns the formatted response.
      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)
        })
      }
    )
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.

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

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