Skip to main content
Glama
shinzo-labs

Gmail MCP

by shinzo-labs
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Hybrid

trash_message

Move an email to trash by providing its message ID, removing it from the inbox.

Instructions

Move a message to the trash

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the message to move to trash

Implementation Reference

  • src/index.ts:676-687 (registration)
    Registration of the 'trash_message' tool on the MCP server via server.tool()
    server.tool("trash_message",
  "Move a message to the trash",
  {
    id: z.string().describe("The ID of the message to move to trash")
  },
  async (params) => {
    return handleTool(config, async (gmail: gmail_v1.Gmail) => {
      const { data } = await gmail.users.messages.trash({ userId: 'me', id: params.id })
      return formatResponse(data)
    })
  }
)
  • src/index.ts:681-686 (handler)
    Handler function for trash_message that calls the Gmail API users.messages.trash with the provided message ID
    async (params) => {
  return handleTool(config, async (gmail: gmail_v1.Gmail) => {
    const { data } = await gmail.users.messages.trash({ userId: 'me', id: params.id })
    return formatResponse(data)
  })
}
  • src/index.ts:678-680 (schema)
    Input schema for trash_message - accepts a single required string parameter 'id' (the message ID to trash)
    {
  id: z.string().describe("The ID of the message to move to trash")
},

Tool Definition Quality

A3.5/5.0
Behavior2/5

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

With no annotations, the description fails to disclose consequences such as reversibility, permission requirements, or side effects on labels. For a mutation tool, this is insufficient.

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 sentence with no redundant words, front-loaded, and efficient.

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?

Given the simple schema and no output schema, the description is minimally complete but lacks behavioral context compared to siblings like delete_message. It could mention recoverability.

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 describes the 'id' parameter with 100% coverage. The description does not add meaning beyond the schema, so baseline 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 the action ('Move') and resource ('a message') with the destination ('to the trash'), distinguishing it from siblings like delete_message (permanent) and untrash_message (reverse).

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 gives no guidance on when to use this tool versus alternatives like delete_message or untrash_message. It is implied for soft deletion, but no explicit context or exclusions are provided.

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/shinzo-labs/gmail-mcp'

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