Skip to main content
Glama

mailroom_move

Move a message to archive, trash, junk, inbox, or a named folder by specifying its message ID and destination folder.

Instructions

Move a message to another folder: archive, trash, junk, inbox, or a named 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": {
      "id": "<id>",
      "to_folder": "<to_folder>"
    },
    "name": "mailroom_move"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesMessage id from mailroom_search (a numeric uid for Gmail/IMAP, a Graph id for Microsoft 365).
folderNoFolder: inbox (default), sent, drafts, trash, junk, archive, all, or a folder name.
accountNoWhich connected mailbox to use (its label from mailroom_accounts). Optional when only one is connected or a default is saved in memory.
to_folderYesDestination: archive, trash, junk, inbox, or a folder name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

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. It indicates a mutation ('Move') and lists destinations, but it does not explain side effects, whether the message is removed from the source folder, account requirements, reversibility, or permissions.

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 description is a single front-loaded sentence with no filler. It is efficient, though it could briefly orient the agent to the account or id context without becoming verbose.

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

Completeness3/5

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

The schema is rich and fully describes the four parameters, and no output schema is needed. However, for a mutation tool with no annotations, the description omits behavioral context such as side effects and account handling, leaving clear gaps.

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 coverage is 100%, so the parameter descriptions already document id, folder, account, and to_folder. The description repeats destination values but does not add meaning beyond the schema, matching the baseline for fully documented parameters.

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 states a specific verb and resource: 'Move a message to another folder,' and lists valid destinations. It is clear what the tool does, but it does not explicitly differentiate itself from nearby mailroom siblings such as mailroom_mark_read or mailroom_forward.

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 gives no explicit guidance about when to use this tool versus alternatives, nor any prerequisites. Moving a message is implied, but there are no stated conditions, exclusions, or sibling comparisons.

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