Skip to main content
Glama

remove_label

Remove a label from an email by providing the message ID and label ID, helping you keep your Gmail inbox organized.

Instructions

Remove a label from an email

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageIdYesEmail message ID
labelIdYesLabel ID to remove

Implementation Reference

  • Zod schema for remove_label tool: validates messageId (string) and labelId (string) input parameters.
    remove_label: z.object({
        messageId: z.string().describe("Email message ID"),
        labelId: z.string().describe("Label ID to remove")
    }),
  • src/tools.ts:44-44 (registration)
    Tool description registered in toolDescriptions map for the 'remove_label' tool.
    remove_label: "Remove a label from an email",
  • Handler case in handleToolCall switch: validates input, calls gmailService.removeLabel(), returns success message.
    case "remove_label": {
        const v = validated as z.infer<typeof schemas.remove_label>;
        await gmailService.removeLabel(v.messageId, v.labelId);
        return { content: [{ type: "text", text: `Label ${v.labelId} removed from email ${v.messageId}.` }] };
    }
  • GmailService.removeLabel() method: calls modifyMessage with removeLabelIds to remove a label from an email via Gmail API.
    async removeLabel(messageId: string, labelId: string): Promise<void> {
        await this.modifyMessage(messageId, { removeLabelIds: [labelId] });
    }
  • Private modifyMessage() helper that calls the Gmail users.messages.modify API endpoint.
    private async modifyMessage(id: string, requestBody: any): Promise<void> {
        await this.gmail.users.messages.modify({ userId: 'me', id, requestBody });
    }
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description bears full responsibility. It only states the action and does not disclose consequences (e.g., mutation, irreversibility, permissions, or error handling).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence that is front-loaded and to the point, with no wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is minimal but adequate for a simple tool with two clear parameters, though it lacks details on return values, error conditions, or 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 coverage is 100% with both parameters described. The description adds no additional meaning beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Remove a label from an email' clearly states the action and resource, distinguishing it from siblings like 'apply_label' which adds a label.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for removing a label from an email, but no explicit guidance on when to use vs alternatives (e.g., batch removal) or prerequisites.

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/muammar-yacoob/GMail-Manager-MCP'

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