Skip to main content
Glama
Sign In
Email MCP Server

Email MCP Server

by 123jixinyu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

move_email

Idempotent

Relocate an email to a different mailbox folder. Provide the email ID, source folder, and destination folder to organize your messages.

Instructions

Move an email to a different mailbox folder. The sourceMailbox must be a real folder, not a virtual one like "All Mail". Use find_email_folder first if the email was discovered in a virtual folder.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "account": "<account>",
      "emailId": "<emailId>",
      "sourceMailbox": "<sourceMailbox>",
      "destinationMailbox": "<destinationMailbox>"
    },
    "name": "move_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountYesAccount name from list_accounts
emailIdYesEmail ID to move (from list_emails)
sourceMailboxYesCurrent mailbox (e.g., INBOX)
destinationMailboxYesTarget mailbox (e.g., Archive). Use list_mailboxes to see options.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.3

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already indicate a non-read-only, non-destructive, idempotent operation. The description adds a meaningful constraint about virtual folders being invalid sources, which is behavioral context beyond the annotations. It doesn't detail failure modes, but the added constraint is valuable.

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 two sentences: the first states the core purpose, and the second provides a crucial constraint and prerequisite. Every word earns its place with no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple move operation with all parameters documented in the schema and safety traits covered by annotations, the description adds the essential caveat about virtual folders and the find_email_folder prerequisite. It is complete enough without an output schema.

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 descriptions cover all four parameters, but the description enhances the meaning of sourceMailbox by clarifying that it must be a real folder, not virtual. This is additional semantic value beyond the structured 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 action with a specific verb ('Move') and resource ('an email') to a destination ('a different mailbox folder'). It distinguishes from sibling tools like delete_email or mark_email by focusing on relocation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit usage guidance: sourceMailbox must be a real folder, and it names find_email_folder as a prerequisite when the email was discovered in a virtual folder. This gives clear contextual direction, though it doesn't mention alternatives like bulk_action for multiple moves.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools