Skip to main content
Glama

untrash_message

Restore accidentally deleted Gmail messages from trash by providing the message ID to recover emails and maintain inbox organization.

Instructions

Remove a message from the trash

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the message to remove from trash

Implementation Reference

  • The handler function for the 'untrash_message' tool. It invokes the shared 'handleTool' helper to authenticate, call the Gmail API's users.messages.untrash method with the provided message ID, and format the response.
      async (params) => {
        return handleTool(config, async (gmail: gmail_v1.Gmail) => {
          const { data } = await gmail.users.messages.untrash({ userId: 'me', id: params.id })
          return formatResponse(data)
        })
      }
    )
  • The Zod input schema for the 'untrash_message' tool, requiring a single 'id' parameter which is the Gmail message ID.
    {
      id: z.string().describe("The ID of the message to remove from trash")
    },
  • src/index.ts:689-700 (registration)
    The MCP server.tool registration for the 'untrash_message' tool, specifying the name, description, input schema, and handler function.
    server.tool("untrash_message",
      "Remove a message from the trash",
      {
        id: z.string().describe("The ID of the message to remove from trash")
      },
      async (params) => {
        return handleTool(config, async (gmail: gmail_v1.Gmail) => {
          const { data } = await gmail.users.messages.untrash({ userId: 'me', id: params.id })
          return formatResponse(data)
        })
      }
    )
  • Shared helper function 'handleTool' used by untrash_message (and other tools) to handle OAuth2 authentication, credential validation, Gmail client creation, API call execution, and standardized 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) {
        // Check for specific authentication errors
        if (
          error.message?.includes("invalid_grant") ||
          error.message?.includes("refresh_token") ||
          error.message?.includes("invalid_client") ||
          error.message?.includes("unauthorized_client") ||
          error.code === 401 ||
          error.code === 403
        ) {
          return formatResponse({
            error: `Authentication failed: ${error.message}. Please re-authenticate by running: npx @shinzolabs/gmail-mcp auth`,
          });
        }
    
        return formatResponse({ error: `Tool execution failed: ${error.message}` });
      }
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Remove from trash' implies a write operation that restores a message, it doesn't specify whether this requires specific permissions, what happens if the message isn't in trash, or what the response looks like. Important behavioral details are missing.

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, efficient sentence that states exactly what the tool does with zero wasted words. It's appropriately sized for a simple operation and front-loads the core functionality.

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 insufficient. It doesn't explain what happens after untrashing (where the message goes), error conditions, or return values. Given the tool's potential side effects, more context is needed.

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%, so the schema already fully documents the single 'id' parameter. The description doesn't add any additional parameter context beyond what's in the schema, making the baseline score of 3 appropriate.

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 ('Remove') and target resource ('a message from the trash'), making the tool's purpose immediately understandable. It doesn't explicitly differentiate from sibling 'untrash_thread', but the distinction is implied by the resource type (message vs thread).

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 'trash_message' (moving to trash). It also doesn't mention prerequisites like needing a message to already be in the trash, leaving usage context unclear.

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