Skip to main content
Glama
mpalermiti

outlook-mcp

by mpalermiti
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

outlook_search_mail

Read-only

Search Outlook emails with KQL across all or one folder to find messages by sender, subject, date, or attachment; set result limits or concise output.

Instructions

Full-text search mail with KQL across all folders (or one, if folder is set).

Use this for "find emails about X"; use outlook_list_inbox for structured filters scoped to a single folder.

Example: outlook_search_mail(query="from:sarah@acme.com received>=2026-01-01", count=10) query is Microsoft KQL (from:, subject:, received>=, hasattachment:true, AND/OR/NOT). Operators must be UPPERCASE — lowercase and is matched as a literal term. Two terms with no operator between them broaden the search; use AND explicitly to narrow. Pass concise=True to drop large fields (preview, categories) — ~10x fewer tokens.

Input Schema

NameRequiredDescriptionDefault
countNo
queryYes
cursorNo
folderNo
conciseNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changedv1.30.2
    • removedInput schema / properties / concise / title
      Removed value: -"Concise"
    • removedInput schema / properties / count / title
      Removed value: -"Count"
    • removedInput schema / properties / cursor / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • removedInput schema / properties / cursor / default
      Removed value: -null
    • removedInput schema / properties / cursor / title
      Removed value: -"Cursor"
    • addedInput schema / properties / cursor / type
      Added value: +"string"
    • removedInput schema / properties / folder / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • removedInput schema / properties / folder / default
      Removed value: -null
    • removedInput schema / properties / folder / title
      Removed value: -"Folder"
    • addedInput schema / properties / folder / type
      Added value: +"string"
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / title
      Removed value: -"outlook_search_mailArguments"
  2. Addedv1.14.0
  3. Removedv1.12.0
  4. First observedv1.11.0

TDQS

A4.4/5.0
Behavior4/5

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

With readOnlyHint already declaring safety, the description adds genuinely non-obvious behavior: uppercase-only operators, lowercase `and` matching as a literal, and implicit broadening of adjacent terms. It omits any mention of result ordering or how `cursor` pages through results, which matters for a search that can exceed `count`.

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?

Front-loaded with purpose and the sibling distinction, then example, then syntax pitfalls, then the token-saving tip — a sensible priority order. Each sentence carries distinct information; nothing is padding.

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, but the `concise` note implicitly tells the agent what fields come back, and the KQL guidance covers the hard part of invocation. The unexplained `cursor` and undocumented `count` default leave paging behavior underspecified for a tool that clearly returns paginated 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 coverage is 0%, so the description carries the full documentation burden, and it does well for three of five parameters: `query` (KQL fields, operator list, examples), `folder` (implicit scoping), and `concise` (drops preview/categories, ~10x token savings). `cursor` is never mentioned and `count` only appears incidentally in the example with no default or max, leaving meaningful gaps.

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 ('Full-text search mail with KQL') plus its scope ('across all folders, or one if `folder` is set'). It explicitly contrasts itself with outlook_list_inbox, so an agent can distinguish the two without opening either schema.

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 ('find emails about X') and names the alternative with the condition that selects it ('use outlook_list_inbox for structured filters scoped to a single folder'). The decision rule is complete and requires no inference.

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