Skip to main content
Glama
Sign In
Gmail MCP Server

Gmail MCP Server

by ampcome-mcps
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

gmail_delete_messages

Delete multiple Gmail messages by providing their IDs. Removes emails permanently from your inbox.

Instructions

Delete Gmail messages.

Args: message_ids: List of message IDs to delete

Returns: Dictionary with operation result

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": {
      "message_ids": "<message_ids>"
    },
    "name": "gmail_delete_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
message_idsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, description fails to disclose whether deletion is permanent, moves to trash, requires specific scopes, or affects conversations; only states 'delete' without added detail.

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

Conciseness3/5

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

Very brief but under-specified; the args/returns structure is clean, but the conciseness comes at the cost of missing critical information.

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

Completeness1/5

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

No annotations or output schema, and the description omits essential details like permanence, batching limits, error handling, and return value interpretation, leaving the agent underinformed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%; description merely restates the parameter type (list of message IDs) with no explanation of how to obtain IDs, format, or constraints, providing no value beyond the schema.

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?

Clearly states 'Delete Gmail messages', specific verb+resource, and distinct from sibling tools like gmail_list_messages or gmail_mark_as_read.

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 on when to use this tool versus alternatives like marking as read or moving to trash; lacks context on prerequisites or irreversibility.

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

Deploy Server

Other Tools