Skip to main content
Glama

delete_label

Remove unwanted labels from your Gmail account to organize your inbox by deleting specific labels using their unique ID.

Instructions

Delete a label

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the label to delete

Implementation Reference

  • src/index.ts:422-433 (registration)
    Registration of the 'delete_label' MCP tool, including description, input schema, and inline handler function that deletes a Gmail label by ID using the Gmail API.
    server.tool("delete_label",
      "Delete a label",
      {
        id: z.string().describe("The ID of the label to delete")
      },
      async (params) => {
        return handleTool(config, async (gmail: gmail_v1.Gmail) => {
          const { data } = await gmail.users.labels.delete({ userId: 'me', id: params.id })
          return formatResponse(data)
        })
      }
    )
  • Handler implementation for 'delete_label' tool. Authenticates via handleTool, calls Gmail API to delete the specified label, and formats the response.
    async (params) => {
      return handleTool(config, async (gmail: gmail_v1.Gmail) => {
        const { data } = await gmail.users.labels.delete({ userId: 'me', id: params.id })
        return formatResponse(data)
      })
    }
  • Input schema for 'delete_label' tool using Zod: requires a string 'id' parameter for the label ID.
    {
      id: z.string().describe("The ID of the label to delete")
    },
  • Shared helper function 'handleTool' used by 'delete_label' (and other tools) to manage OAuth2 authentication, create Gmail client, execute the API call, and handle errors.
    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}`
      }
    }
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. 'Delete a label' implies a destructive mutation, but it doesn't disclose whether deletion is permanent, reversible, requires specific permissions, or has side effects (e.g., affecting messages with that label). For a destructive tool with zero annotation coverage, this is a significant gap in behavioral context.

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 extremely concise with just three words, front-loading the essential action. There's zero waste or redundancy. For a simple delete operation, this brevity is appropriate and efficient.

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 this is a destructive mutation tool with no annotations and no output schema, the description is inadequate. It doesn't explain what happens after deletion (e.g., success/failure response, error conditions), whether the action is idempotent, or how it interacts with sibling tools. The simplicity of the tool (one parameter) doesn't compensate for the lack of behavioral 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 'id' fully documented in the schema as 'The ID of the label to delete'. The description adds no additional parameter information beyond what the schema provides. With high schema coverage, the baseline score of 3 is appropriate as the description doesn't compensate but doesn't need to.

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 verb ('delete') and resource ('label'), making the purpose immediately understandable. It distinguishes from sibling tools like 'patch_label' and 'update_label' by specifying deletion rather than modification. However, it doesn't specify what kind of label (e.g., Gmail label) or provide additional context about the resource being deleted.

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 like 'patch_label' or 'update_label' for modifying labels instead of deleting them. There's no mention of prerequisites (e.g., needing the label ID) or consequences of deletion. 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/HitmanLy007/gmail-mcp'

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