Skip to main content
Glama

remove_delegate

Remove a delegate's access to manage your Gmail account by specifying their email address.

Instructions

Removes the specified delegate

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
delegateEmailYesEmail address of delegate to remove

Implementation Reference

  • Handler function for remove_delegate tool: calls Gmail API to delete the specified delegate email address using handleTool wrapper for authentication.
      async (params) => {
        return handleTool(config, async (gmail: gmail_v1.Gmail) => {
          const { data } = await gmail.users.settings.delegates.delete({ userId: 'me', delegateEmail: params.delegateEmail })
          return formatResponse(data)
        })
      }
    )
  • Input schema for remove_delegate tool: requires delegateEmail string.
    {
      delegateEmail: z.string().describe("Email address of delegate to remove")
    },
  • src/index.ts:961-972 (registration)
    Registration of the remove_delegate tool on the MCP server, including description, schema, and handler.
    server.tool("remove_delegate",
      "Removes the specified delegate",
      {
        delegateEmail: z.string().describe("Email address of delegate to remove")
      },
      async (params) => {
        return handleTool(config, async (gmail: gmail_v1.Gmail) => {
          const { data } = await gmail.users.settings.delegates.delete({ userId: 'me', delegateEmail: params.delegateEmail })
          return formatResponse(data)
        })
      }
    )
  • Helper function handleTool used by remove_delegate to handle 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 the API response for the MCP tool output.
    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?

No annotations are provided, so the description carries full burden. 'Removes' implies a destructive mutation, but it doesn't disclose whether this requires special permissions, if the action is reversible, what happens to associated data, or any rate limits. For a mutation tool with zero annotation coverage, this is inadequate behavioral disclosure.

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 and front-loads the core action, making it easy to parse quickly.

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 destructive mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what 'delegate' means in this system, what the removal entails, or what the agent should expect as a result. The context signals show minimal complexity, but the description fails to provide necessary operational context.

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 additional parameter information beyond what the schema provides, so it meets the baseline score of 3 where 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 'Removes the specified delegate' clearly states the action (removes) and the resource (delegate), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'delete_delegate' (which doesn't exist) 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?

The description provides no guidance on when to use this tool versus alternatives. With sibling tools like 'list_delegates' and 'get_delegate', there's no indication whether removal should follow verification or what prerequisites exist. 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