Skip to main content
Glama

graph_move_mail

Move up to 50 Outlook messages to a specified mail folder, such as archive or deleted items, and report each message’s outcome so partial failures remain clear.

Instructions

Move messages to a mail folder. Use this to archive mail.

Processes each message in order and reports per-message outcomes, so a partial failure still tells you what moved.

Args: message_ids: Message IDs to move (1-50 per call). destination_folder: Destination folder ID or well-known name (default "archive"). Common: archive, inbox, deleteditems, junkemail. mailbox: Shared mailbox address or user ID to act on. Empty targets your own mailbox. Requires the delegated Mail.*.Shared permissions.

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_ids": "<message_ids>"
    },
    "name": "graph_move_mail"
  }
}

Input Schema

NameRequiredDescriptionDefault
mailboxNo
message_idsYes
destination_folderNoarchive

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses ordered per-message processing, per-message outcome reporting on partial failure, and that the shared-mailbox mode requires delegated Mail.*.Shared permissions. It stops short of saying whether messages leave the source folder, whether the operation is idempotent, or what happens to already-located messages, which are meaningful gaps for a relocating mutation.

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?

Front-loaded with the action and use case, then the args in parameter order. The Args block is readable and mostly earns its place, though the parenthetical detail on destination_folder is slightly denser than needed and the archive guidance is somewhat redundant with the opening sentence.

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?

No output schema exists, and the description compensates by describing the per-message outcome reporting. Combined with full parameter coverage and the permission note, an agent has enough to call it correctly; only failure semantics (abort vs continue) are left implicit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/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 compensate and does: message_ids is bounded to 1-50 per call, destination_folder's default and the well-known names (archive, inbox, deleteditems, junkemail) are enumerated, and mailbox's empty-means-your-own semantics plus permission requirement are spelled out. This adds substantial meaning beyond the bare JSON schema.

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 to a mail folder") and adds a concrete use case (archiving). It is clearly distinct from graph_move_file by resource, but it does not name or contrast any sibling tool explicitly.

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?

"Use this to archive mail" gives one implied scenario, but there is no when-not guidance and no named alternative (e.g., graph_categorize_mail, delete, or copy) for cases where the caller doesn't want to relocate messages. Usage is inferable but not framed against alternatives.

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