Skip to main content
Glama

Move messages

move_messages

Move Outlook messages to another folder such as archive or a custom path. Message IDs stay valid after moving, so follow-up actions keep working.

Instructions

Move messages to another folder (e.g. archive). Message IDs stay valid after moving.

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": {
      "ids": "<ids>",
      "destination": "<destination>"
    },
    "name": "move_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesMessage IDs (from list_messages, search_messages or get_message)
destinationYesDestination folder. Accepts a well-known name (inbox, drafts, sentitems/sent, deleteditems/trash, junkemail/junk, archive, outbox), a display name or path such as "Inbox/Projects", or a folder ID from list_folders

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the safety profile is covered by structured data. The description adds one genuinely useful post-condition — 'Message IDs stay valid after moving' — which an agent cannot get from annotations, but it says nothing about permissions, partial-failure behavior, or what happens if the destination doesn't exist.

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?

Two tight sentences with the action stated first and the ID-stability guarantee second. The '(e.g. archive)' aside mildly duplicates what the schema already enumerates, but nothing is wasted.

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?

For a simple two-parameter tool with full schema coverage and annotations, the description is adequate but thin: it omits what happens on partial or failed moves and whether the destination must pre-exist. Those gaps are modest given no output schema exists to explain results.

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 both ids and destination fully documented including accepted name formats. The description adds only the archive example, so the schema is doing nearly all the work; baseline 3 applies.

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?

States a specific verb and resource ('Move messages') plus the destination scope ('to another folder'), which is enough to separate it from siblings like copy_messages or delete_messages. It does not explicitly name a sibling, so it stops short of a 5.

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?

There is no guidance on when to prefer moving over copying, deleting or categorizing, and no stated preconditions (e.g. destination folder must exist). The use case is only inferable from the tool name and the parenthetical '(e.g. archive)'.

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