Skip to main content
Glama
owlpost

owlpost

move_email

Destructive

Move an email from one folder to another using IMAP, with automatic fallback to copy-and-delete when MOVE is unsupported.

Instructions

Move a message from one folder to another.

Uses IMAP MOVE when the server supports it, otherwise COPY followed by flagging the original \Deleted and EXPUNGE. The message gets a new UID in the destination folder, so the old uid is no longer valid afterwards.

Args: account: Account name from list_accounts. folder: Folder the message is currently in. uid: Message UID in that folder. dest_folder: Destination folder name (see list_folders).

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>",
      "folder": "<folder>",
      "uid": "<uid>",
      "dest_folder": "<dest_folder>"
    },
    "name": "move_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
uidYes
folderYes
accountYes
dest_folderYes

Output Schema

NameRequiredDescriptionDefault
toYes
uidYes
fromYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "from": {
      +      "title": "From",
      +      "type": "string"
      +    },
      +    "to": {
      +      "title": "To",
      +      "type": "string"
      +    },
      +    "uid": {
      +      "title": "Uid",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "uid",
      +    "from",
      +    "to"
      +  ],
      +  "title": "MoveResult",
      +  "type": "object"
      +}
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior5/5

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

The description goes well beyond the annotations by disclosing the implementation: IMAP MOVE when supported, otherwise COPY plus \Deleted flag and EXPUNGE on the original. It also warns that the message receives a new UID in the destination and the old uid becomes invalid, which is critical behavioral context an agent cannot get from destructiveHint=false/true flags alone.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening sentence front-loads the action, followed by the most decision-relevant behavioral caveat (UID invalidation). The Args block is slightly redundant with the schema titles but each line adds real meaning, so almost nothing is wasted.

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 destructive, non-idempotent mutation the description covers mechanism, side effects on UIDs, and parameter sourcing, and an output schema exists so return values need no explanation. Remaining gaps are failure modes such as a nonexistent dest_folder or a message that cannot be expunged, which would round it out to a 5.

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 0%, so the description must carry parameter meaning, and it largely does: account is tied to list_accounts, folder is defined as the message's current folder, uid is scoped to that folder, and dest_folder points at list_folders. It does not specify the UID string format or whether dest_folder must already exist, so it falls just short of fully compensating.

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 opens with a specific verb and resource: 'Move a message from one folder to another.' That is unambiguous and clearly distinct from sibling mutations such as delete_email or flag_message. It stops short of explicitly contrasting itself with any named sibling, so it lands at 4 rather than 5.

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?

Usage is only implied: an agent infers it should call this when a message needs relocating. There is no explicit when-to-use/when-not-to-use guidance and no mention of alternatives (e.g., copy semantics or delete_email for removal). The references to list_accounts and list_folders help with prerequisites but are not usage routing.

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