Skip to main content
Glama

trash_message

Move Gmail messages to trash to declutter your inbox and manage email storage. Specify the message ID to permanently remove unwanted emails.

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:643-654 (registration)
    Registration of the trash_message tool using McpServer.tool, defining its name, description, input schema (message ID), and inline handler function that uses the Gmail API to move the message to trash.
    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)
        })
      }
    )
  • The handler function for trash_message tool, which invokes handleTool to authenticate and call gmail.users.messages.trash API 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)
      })
    }
  • Input schema for trash_message tool using Zod: requires a string 'id' parameter for the message ID.
    {
      id: z.string().describe("The ID of the message to move to trash")
    },
  • Shared helper function handleTool used by trash_message (and other tools) to manage OAuth2 authentication, credential validation, Gmail client creation, and API call execution with error handling.
    const handleTool = async (queryConfig: Record<string, any> | undefined, apiCall: (gmail: gmail_v1.Gmail) => Promise<any>) => {
      try {
        const oauth2Client = queryConfig ? createOAuth2Client(queryConfig) : defaultOAuth2Client
        if (!oauth2Client) throw new Error('OAuth2 client could not be created, please check your credentials')
    
        const credentialsAreValid = await validateCredentials(oauth2Client)
        if (!credentialsAreValid) throw new Error('OAuth2 credentials are invalid, please re-authenticate')
    
        const gmailClient = queryConfig ? google.gmail({ version: 'v1', auth: oauth2Client }) : defaultGmailClient
        if (!gmailClient) throw new Error('Gmail client could not be created, please check your credentials')
    
        const result = await apiCall(gmailClient)
        return result
      } catch (error: any) {
        return `Tool execution failed: ${error.message}`
      }
    }
  • Helper function formatResponse used to standardize tool responses into MCP content format by JSON stringifying the API response.
    const formatResponse = (response: any) => ({ content: [{ type: "text", text: JSON.stringify(response) }] })
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 the trash') but lacks details on permissions required, whether the operation is reversible, if it affects related data (e.g., threads), or typical response behavior. This leaves significant gaps for a mutation tool.

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, direct sentence with zero wasted words, making it easy to parse and understand immediately. It's appropriately sized for a simple tool with one parameter and no complex behavior to explain.

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?

For a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't cover behavioral aspects like reversibility, permissions, or error conditions, nor does it explain what happens after trashing (e.g., if the message remains accessible). Given the context, more detail is needed 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?

Schema description coverage is 100%, with the parameter 'id' clearly documented in the schema as 'The ID of the message to move to trash'. The description doesn't add any additional meaning beyond this, such as ID format or sourcing, but the schema provides adequate baseline information.

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 target 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 more specific language about scope or permanence.

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' (permanent deletion) or 'untrash_message' (reversal). It also doesn't mention prerequisites, such as whether the message must be accessible or owned by the user, leaving the agent with insufficient context for decision-making.

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

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