ms-graph-mcp

mail_search

Read-onlyIdempotent

Search emails by keyword, subject, or sender, returning newest matches with previews from inbox, sent, drafts, or all folders.

Instructions

Search the signed-in user's mailbox by keyword, subject or sender name. Returns id, subject, sender, date and a preview snippet, newest first. Searchable folders are inbox, sentitems, drafts, or all. Use mail_list_recent when the ask is time-based rather than keyword-based, and mail_get_thread to read a whole conversation. Requires Mail.Read.

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": {
      "query": "<query>"
    },
    "name": "mail_search"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes	Search keywords, subject, or sender name
`folder`	No	Mail folder: inbox \| sentitems \| drafts \| all	inbox
`max_results`	No	Maximum emails to return (1–50)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 5, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond annotations, the description discloses the return structure ('Returns id, subject, sender, date and a preview snippet'), ordering ('newest first'), folder constraints, and permission requirement ('Requires Mail.Read'). This adds substantial behavioral context without contradicting the readOnly, idempotent annotations.

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?

The description is three sentences, front-loaded with the core purpose, and every sentence adds value: purpose, return/ordering, alternatives, and permissions. There is no redundancy or fluff.

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

Completeness5/5

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

The description thoroughly covers the tool's behavior—search scope, output fields, ordering, folder options, permission requirements, and sibling tool alternatives—despite lacking an output schema. It provides enough context for an agent to select and invoke the tool correctly.

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?

The input schema already covers all parameters with clear descriptions, so the baseline is 3. The description does reinforce query semantics and folder enumeration but adds little beyond the schema's own parameter documentation.

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?

The description clearly states the tool's function: 'Search the signed-in user's mailbox by keyword, subject or sender name.' It specifies the resource (mailbox), the action (search), and the fields searched, and it distinguishes itself from sibling tools by naming alternatives.

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?

The description provides explicit usage guidance: 'Use mail_list_recent when the ask is time-based rather than keyword-based, and mail_get_thread to read a whole conversation.' It also explains the scope of searchable folders, giving clear context for when to use this tool.

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