m365-mcp

Move Item

m365_move

Move an email, mail folder, contact, or OneDrive item to another folder. Returns a new ID for moved emails and contacts for later calls.

Instructions

Move an email, mail folder, contact or OneDrive item to another folder. Moving an email to 'archive' archives it; moving a contact places it in a contact folder. Moved emails and contacts get a new ID, which is returned: use it for later calls.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Item to move.
`new_name`	No	drive_item only: rename while moving.
`resource`	Yes	Type of item.
`account_id`	No	Account ID or email address. Omit when only one account is signed in.
`destination_id`	No	Destination folder. email: mail folder ID or alias (archive, inbox, junk, deleted, drafts, sent). email_folder: mail folder ID or 'root'. contact: contact folder ID or 'default'. drive_item: folder ID or 'root'.
`destination_path`	No	drive_item only: destination folder path instead of destination_id.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes
`status`	Yes
`summary`	Yes	One-line human summary. The tool's text content is this result serialized as JSON (summary included), so a client that ignores structuredContent still sees every field.
`resource`	Yes
`previous_id`	Yes
`destination_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.0.0Sep 29, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations declare non-readOnly, non-idempotent, non-destructive, openWorld. The description adds a genuinely useful behavioral fact not in the structured data: moved emails and contacts receive a NEW id that is returned and must be used for later calls. That identity-change side effect is exactly the kind of context an agent needs after a mutation.

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 tight sentences, front-loaded with the action and accepted resources, followed by the per-resource behavior and the id-change consequence. Zero filler.

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?

With annotations carrying the safety profile and an output schema present, the description needn't explain return values, yet it helpfully flags the returned new id. Coverage is strong; only the absence of usage routing against siblings leaves a small gap.

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% and every parameter (id, new_name, resource, account_id, destination_id, destination_path) is already documented in the schema. The description's per-resource destination nuance ('archive' archives) adds only marginal value beyond that baseline.

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 ('Move') and enumerates the exact resource types it accepts (email, mail folder, contact, OneDrive item), matching the schema enum. It stops short of distinguishing itself from the sibling m365_update, which an agent might otherwise confuse for relocating items.

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?

Provides implied usage guidance by explaining what happens per resource type (email to 'archive' archives it, a contact goes into a contact folder), but never states when to choose this over m365_update or drive_copy, nor any prerequisites such as required permissions.

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