Skip to main content
Glama
faithk7

Gmail MCP Server

by faithk7
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Hybrid

trash_message

Move unwanted Gmail messages to trash using message ID to declutter your inbox and manage email organization.

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' MCP tool, including input schema (message ID) and handler that uses the Gmail API to move the specified message to trash via the shared handleTool wrapper.
    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)
    The handler function for the 'trash_message' tool. It invokes the shared handleTool utility with the Gmail API call to trash the message identified by the provided 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 the 'trash_message' tool using Zod: requires a string 'id' parameter for the Gmail message ID.
    {
  id: z.string().describe("The ID of the message to move to trash")
},

Tool Definition Quality

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('Move to trash') but doesn't explain what 'trash' means operationally (e.g., reversible vs. permanent, retention period, or if it's equivalent to deletion). This leaves gaps in understanding the tool's behavior.

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, clear sentence with no wasted words, making it highly efficient and front-loaded. It directly communicates the tool's purpose without unnecessary elaboration.

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 the lack of annotations and output schema, the description is insufficient for a mutation tool. It doesn't cover behavioral aspects like reversibility, side effects, or error conditions, leaving the agent with incomplete context for safe and effective use.

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 description coverage is 100%, with the single parameter 'id' fully documented in the schema. The description adds no additional meaning beyond what the schema provides, such as format examples or constraints, so it meets the baseline of 3.

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 action ('Move') and resource ('a message to the trash'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'delete_message' or 'trash_thread', which would require a 5.

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 'delete_message' or 'untrash_message'. It lacks context about prerequisites, such as whether the message must be in the inbox or if it can be trashed from any folder.

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

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