Skip to main content
Glama
0x8687

Meme MCP Server

by 0x8687

move-to-trash

Delete unwanted emails by moving them to trash using email IDs. This tool helps manage email clutter by removing selected messages from your inbox.

Instructions

Move emails to trash

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailIdsYesArray of email IDs to move to trash

Implementation Reference

  • The async handler function that executes the move-to-trash tool logic by delegating to toolset.executeAction with 'GMAIL_MOVE_TO_TRASH' action.
    }, async (args, extra) => {
        try {
            const userAddress = "default-user";
            
            const result = await toolset.executeAction({
                action: "GMAIL_MOVE_TO_TRASH",
                entityId: userAddress,
                params: args
            });
            
            if (result.successful) {
                return {
                    content: [{ 
                        type: "text", 
                        text: `🗑️ Emails moved to trash successfully!\n\nMoved ${args.emailIds.length} email(s) to trash.` 
                    }],
                };
            } else {
                return {
                    content: [{ 
                        type: "text", 
                        text: `❌ Failed to move emails to trash: ${result.error || 'Unknown error'}` 
                    }],
                };
            }
        } catch (error) {
            console.error('Error moving emails to trash:', error);
            return {
                content: [{ 
                    type: "text", 
                    text: `Error moving emails to trash: ${error instanceof Error ? error.message : String(error)}` 
                }],
            };
        }
    });
  • Zod input schema for the tool parameters: array of email ID strings.
    emailIds: z.array(z.string()).describe("Array of email IDs to move to trash"),
  • src/tools.ts:610-612 (registration)
    Registration of the 'move-to-trash' tool with server.tool, specifying name, description, schema, and handler reference.
    server.tool("move-to-trash", "Move emails to trash", {
        emailIds: z.array(z.string()).describe("Array of email IDs to move to trash"),
    }, async (args, extra) => {
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. It states the action but doesn't mention whether this is reversible, if it requires specific permissions, what happens to emails in trash (e.g., auto-deletion), or error handling. 'Move to trash' implies a soft delete, but this isn't explicitly clarified.

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 extremely concise at three words 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?

For a mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what happens after moving to trash, whether the operation is atomic, what errors might occur, or what the return value might be. The context signals indicate a simple tool, but more behavioral 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%, with the parameter 'emailIds' clearly documented in the schema as 'Array of email IDs to move to trash'. The description doesn't add any additional meaning beyond what the schema already provides, so it meets the baseline for high coverage.

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 'Move emails to trash' clearly states the action (move) and target resource (emails) with a specific destination (trash). It distinguishes from siblings like 'delete' or 'archive' by specifying trash, but doesn't explicitly differentiate from other email management tools beyond the obvious verb.

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?

No guidance is provided on when to use this tool versus alternatives like deleting permanently or archiving. The description only states what it does, not when it's appropriate or what prerequisites might exist (e.g., needing valid email IDs).

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/0x8687/mcp-gmail-v1'

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