Skip to main content
Glama

graph_mark_mail_read

Mark Outlook messages as read or unread in your own or a shared mailbox. Update up to 50 message IDs per call and get a per-message outcome report.

Instructions

Mark messages as read or unread.

Processes each message in order and reports per-message outcomes.

Args: message_ids: Message IDs to update (1-50 per call). is_read: Whether the messages are read (default true). Use false to mark them unread. 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_mark_mail_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
is_readNo
mailboxNo
message_idsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A3.8/5.0
Behavior3/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 disclose useful behavior: messages are processed in order, per-message outcomes are reported, and delegated Mail.*.Shared permissions are needed for shared mailboxes. It stops short of stating partial-failure semantics (does one bad ID abort the batch?), idempotency, or return format.

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?

The two-sentence summary and per-message note come first, then a compact Args block with one line per parameter. Every line adds information, though the Args formatting is slightly more verbose than a single prose sentence would be.

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 three-parameter, no-output-schema mutation tool this covers purpose, parameter meaning, batch limits, and auth needs adequately. The remaining hole is failure/response behavior, which matters because no output schema exists to describe per-message outcomes.

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%, yet the Args block fully compensates: message_ids is documented with the 1-50 batch bound, is_read with its boolean meaning and default true, and mailbox with its default empty-string behavior plus the permission requirement. An agent can supply all three parameters correctly from the description alone.

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?

The description opens with a specific verb+resource: 'Mark messages as read or unread', naming the operation and the toggle direction. It does not explicitly name a sibling such as graph_mark_chat_read or graph_flag_mail, but the mail-message scope keeps it distinguishable.

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?

It gives conditional guidance for one parameter ('Use false to mark them unread', 'Empty targets your own mailbox') and states the permission prerequisite for shared mailboxes. It does not say when to prefer this over related tools like graph_mark_chat_read or graph_flag_mail, so usage is implied rather than routed.

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