Skip to main content
Glama

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
NameRequiredDescriptionDefault
delegateEmailYesEmail address of delegate to add

Implementation Reference

  • 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)
      })
    }
  • 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)
        })
      }
    )
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 this is an 'Adds' operation (implying mutation) but doesn't disclose what permissions are required, whether this is reversible, what happens on duplicate attempts, or what the expected response looks like. For a mutation tool with zero annotation coverage, this is inadequate.

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 that states the core functionality without any wasted words. It's appropriately sized for a simple tool and gets straight to the point with no 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 insufficient. It doesn't explain what a delegate is, what permissions are required, what happens on success/failure, or how this relates to sibling tools. The agent would need to guess about important behavioral aspects of this write operation.

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' well-documented in the schema. The description doesn't add any parameter-specific information beyond what's already in the structured schema, so it meets the baseline for high schema coverage without adding extra value.

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 target resource ('a delegate to the specified account'), making the purpose immediately understandable. However, it doesn't differentiate from its sibling 'remove_delegate' or explain what a delegate is in this context, preventing a perfect score.

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 like 'list_delegates' or 'remove_delegate'. The description doesn't mention prerequisites, permissions needed, or typical use cases, leaving the agent to infer usage context 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/faithk7/gmail-mcp'

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