Outlook MCP Server

Overview Schema Source Related Servers Discussions Admin

report_junk

Reports messages as spam, trains Outlook's filter, blocks senders, and moves them to Junk by default to stop unwanted mail.

Instructions

Report messages as spam: trains Outlook's filter, adds each sender to the blocked senders list and, by default, moves the messages to Junk.

Use it when the user wants no more mail from the sender; moving to junkemail with move_messages only files the message. For newsletters the user once signed up for, unsubscribe is the better first step. confirm_count: must equal the number of ids; show the user the list first.

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": "report_junk"
  }
}

Input Schema

Name	Required	Description	Default
`message_ids`	Yes
`move_to_junk`	No
`confirm_count`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 9, 2026

TDQS

A4.5/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 the three side effects (filter training, blocked-senders list, Junk move) and that the Junk move is the default. It stops short of saying whether the block is reversible or what permissions are needed, which keeps it from a 5.

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?

Three short, front-loaded blocks with no filler; the effect list comes first, then routing guidance, then the safety check. Minor deduction for the awkward line break splitting 'the blocked senders list' and the slightly compressed final 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?

For a 3-parameter mutation tool with no annotations and no output schema, the description covers effects, alternatives, and the confirmation guardrail. Only the return value and reversibility of the block are unaddressed, which is a small gap.

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 coverage is 0%, so the description must compensate, and it does for two of three parameters: move_to_junk's default behavior is explained and confirm_count is given a precise constraint ('must equal the number of ids') plus a workflow instruction. message_ids is only implied by 'each sender'/'the messages' rather than described.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Report messages as spam') and immediately enumerates the concrete effects: trains the filter, blocks the sender, moves to Junk. It is clearly distinguishable from move_messages and unsubscribe, which it names.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit when-to-use condition ('when the user wants no more mail from the sender') and names two alternatives with the reason to prefer each: move_messages only files the message, and unsubscribe is the better first step for newsletters.

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