Skip to main content
Glama
faithk7

Gmail MCP Server

by faithk7
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Hybrid

trash_thread

Move email threads to trash in Gmail to organize your inbox by removing unwanted conversations.

Instructions

Move a thread to the trash

Input Schema

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

Implementation Reference

  • src/index.ts:810-816 (handler)
    The handler function for the 'trash_thread' tool. It uses the Gmail API to move the specified thread to the trash by calling gmail.users.threads.trash with the provided thread ID.
      async (params) => {
    return handleTool(config, async (gmail: gmail_v1.Gmail) => {
      const { data } = await gmail.users.threads.trash({ userId: 'me', id: params.id })
      return formatResponse(data)
    })
  }
)
  • src/index.ts:807-809 (schema)
    The input schema for the 'trash_thread' tool, defined using Zod. It requires a single 'id' parameter which is the thread ID.
    {
  id: z.string().describe("The ID of the thread to move to trash")
},
  • src/index.ts:805-816 (registration)
    The registration of the 'trash_thread' tool on the MCP server using server.tool, including description, schema, and handler.
    server.tool("trash_thread",
  "Move a thread to the trash",
  {
    id: z.string().describe("The ID of the thread to move to trash")
  },
  async (params) => {
    return handleTool(config, async (gmail: gmail_v1.Gmail) => {
      const { data } = await gmail.users.threads.trash({ userId: 'me', id: params.id })
      return formatResponse(data)
    })
  }
)

Tool Definition Quality

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Move to the trash' implies a destructive but potentially reversible action, but the description doesn't clarify if this requires specific permissions, whether it's reversible (hinting at 'untrash_thread'), what happens to associated messages, or if there are rate limits. 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—'Move a thread to the trash'—making it front-loaded and easy to parse. Every word earns its place by directly conveying the tool's action and target.

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 complexity of a destructive operation with no annotations and no output schema, the description is incomplete. It lacks crucial details like behavioral traits (e.g., reversibility, permissions), usage context versus siblings, and expected outcomes, which are essential for safe and effective tool invocation.

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 as 'The ID of the thread to move to trash'. The description doesn't add any additional meaning beyond this, so it meets the baseline of 3 where the schema does the heavy lifting.

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 thread to the trash'), making the purpose immediately understandable. It distinguishes from siblings like 'delete_thread' (permanent deletion) and 'untrash_thread' (restoration), though it doesn't explicitly name these alternatives in the description itself.

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_thread' (permanent deletion) or 'trash_message' (for individual messages). It also doesn't mention prerequisites, such as whether the thread must exist or be accessible.

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