Skip to main content
Glama

messages_move

Move an e-mail message to another folder of the real mailbox (the provider's own Archive, Inbox or a folder by its exact name). Works on mailboxes connected over IMAP/SMTP (e.g. Yahoo); other channels, and Gmail accounts connected read-only, refuse. To delete a message use messages.delete (it moves to the Trash).

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": {
      "message_id": "<message_id>",
      "folder": "<folder>"
    },
    "name": "messages_move"
  }
}

Input Schema

NameRequiredDescriptionDefault
folderYesDestination: "archive", "inbox" or the exact folder name in the mailbox.
message_idYesID of the e-mail message (from messages.read_history).
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=false, so the safety profile is covered. The description adds real value beyond that by disclosing the channel/account preconditions under which the call is refused, which annotations cannot express. It stops short of saying what happens if the destination folder does not exist or what a failure looks like.

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?

Three sentences, front-loaded with the action and destination, then the preconditions, then the delete alternative. Every sentence carries distinct information with no repetition.

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

Completeness4/5

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

For a three-parameter mutation with no output schema, the description covers the action, the destination semantics, the account preconditions, and the sibling alternative. The only gap is failure behavior when the target folder is absent, which is minor given the annotations already flag it as non-destructive and non-idempotent.

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 all three parameters are already documented, including the folder destination values and the message_id source. The description restates the folder semantics (provider's own Archive, Inbox, or exact folder name) but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ("Move an e-mail message to another folder") and scopes it to the real mailbox, naming the provider's Archive/Inbox or an exact folder name. It also explicitly distinguishes itself from messages.delete, so an agent can tell the two apart without opening either schema.

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

Usage Guidelines5/5

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

Gives explicit when-it-works conditions (mailboxes connected over IMAP/SMTP, e.g. Yahoo) and when-it-refuses conditions (other channels, Gmail connected read-only). It also names the alternative for a different intent: use messages.delete to delete, which moves to Trash.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.