Skip to main content
Glama

untrash_thread

Restore email threads from the trash in Gmail by providing the thread ID to recover deleted conversations.

Instructions

Remove a thread from the trash

Input Schema

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

Implementation Reference

  • src/index.ts:804-815 (registration)
    Registration of the 'untrash_thread' tool. Includes input schema (thread ID) and inline handler that uses the Gmail API to untrash the specified thread via gmail.users.threads.untrash. Relies on shared 'handleTool' and 'formatResponse' utilities.
    server.tool("untrash_thread",
      "Remove a thread from the trash",
      {
        id: z.string().describe("The ID of the thread to remove from trash")
      },
      async (params) => {
        return handleTool(config, async (gmail: gmail_v1.Gmail) => {
          const { data } = await gmail.users.threads.untrash({ userId: 'me', id: params.id })
          return formatResponse(data)
        })
      }
    )
  • The handler function for 'untrash_thread' tool. It invokes the shared 'handleTool' which handles OAuth, validates credentials, creates Gmail client, calls the Gmail API's threads.untrash method with the provided thread ID, and formats the response.
    async (params) => {
      return handleTool(config, async (gmail: gmail_v1.Gmail) => {
        const { data } = await gmail.users.threads.untrash({ userId: 'me', id: params.id })
        return formatResponse(data)
      })
  • Input schema for 'untrash_thread' tool using Zod: requires a single 'id' parameter which is the thread ID.
    {
      id: z.string().describe("The ID of the thread to remove from trash")
    },
  • Shared 'handleTool' helper used by 'untrash_thread' and other tools. Manages OAuth2 client creation, credential validation, Gmail client instantiation, executes the provided API call, and handles errors.
    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}`
      }
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the action ('Remove from trash') but doesn't disclose behavioral traits like whether this requires specific permissions, what happens if the thread isn't in trash, if the operation is reversible, or what the response looks like. For a mutation tool with zero annotation coverage, this is a significant gap.

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 with zero waste. It's front-loaded with the core action and resource, making it immediately understandable 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 tool's mutation nature (restoring from trash), no annotations, no output schema, and incomplete behavioral disclosure, the description is inadequate. It should explain more about the operation's effects, error conditions, or return values to help an agent use it correctly.

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

Parameters4/5

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

Schema description coverage is 100% (the 'id' parameter is fully documented in the schema), so the baseline is 3. The description doesn't add parameter-specific details beyond what the schema provides, but with only one parameter, the lack of additional semantics is less critical. It implies the 'id' refers to a thread, which aligns with 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?

The description clearly states the specific action ('Remove') and target resource ('a thread from the trash'), distinguishing it from sibling tools like 'untrash_message' (which operates on messages) and 'trash_thread' (which moves threads to trash). It uses precise terminology that matches the tool name without being tautological.

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 implies usage context (when a thread is in the trash and needs restoration) but doesn't explicitly state when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., thread must be in trash) or exclusions (e.g., cannot be used on permanently deleted threads), leaving some ambiguity.

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

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