Gmail Multi-Inbox MCP Server

delete_label

Delete a Gmail label from a designated account by providing the account ID and label ID.

Instructions

Delete a Gmail label in one account (account required).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "account": "<account>",
      "label_id": "<label_id>"
    },
    "name": "delete_label"
  }
}

Input Schema

Name	Required	Description	Default
`account`	Yes	Account id.
`label_id`	Yes	Label id to delete.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.6.2Aug 14, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of disclosing behavioral traits. For a destructive operation like deletion, it fails to mention that the action is permanent, whether messages are affected, or if special permissions are needed. The description only restates the basic purpose.

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 with no filler words. It front-loads the core purpose and includes a necessary prerequisite hint ('account required'). It is appropriately sized for a simple delete operation, though it could include more detail without becoming verbose.

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 that this is a destructive tool with no output schema or annotations, the description should provide caveats about permanence and clarify the difference from similar tools like remove_labels. The current description is too minimal to fully guide an agent, especially in a context-rich environment with many sibling tools.

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 schema already provides full descriptions (100% coverage) for both parameters (account and label_id). The description adds no additional semantic meaning beyond what the schema states, so the baseline score of 3 is appropriate.

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 clearly states a specific action ('Delete a Gmail label') on a specific resource, which differentiates it from sibling tools like create_label or get_labels. The phrase 'in one account' adds scope clarity.

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 deleting a label from a single account, but provides no explicit guidance on when to use this tool versus alternatives like remove_labels (which removes labels from messages) or create_label. It mentions 'account required' as a prerequisite, but lacks exclusionary context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server