Skip to main content
Glama

Mark read/unread

mark_messages_read

Mark one or more Outlook messages as read or unread by ID, without sending read receipts. Use it to update message status after reviewing or triaging mail in Microsoft 365.

Instructions

Mark messages as read or unread (no read receipts are sent).

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": {
      "ids": "<ids>",
      "read": "<read>"
    },
    "name": "mark_messages_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesMessage IDs (from list_messages, search_messages or get_message)
readYestrue = read, false = unread

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the mutation/safety profile is covered structurally. The description adds one genuinely non-obvious behavior — no read receipts are sent — which is useful privacy context not present in the schema or annotations. It omits idempotency, partial-failure behavior for invalid IDs, and whether the change is reversible, so it stays at solid-but-partial.

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?

A single front-loaded sentence with the action first and the caveat second; nothing is wasted and nothing important is buried.

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 two-parameter, non-destructive toggle with full schema descriptions and an annotation-supplied safety profile, the definition covers what an agent needs to call it correctly. The only thin area is outcome reporting, but no output schema exists to require it.

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%: 'ids' documents its source tools and 1-500 bounds, and 'read' documents true=read/false=unread. The description adds no meaning beyond that, which is the expected baseline when the schema carries the parameter burden.

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+resource pair ('Mark messages as read or unread') that an agent can map directly to the ids/read schema. It doesn't differentiate from adjacent siblings such as flag_messages, but the action itself is unambiguous.

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

Usage Guidelines2/5

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

No when-to-use guidance, no prerequisites, and no mention of alternatives (e.g., flagging versus reading). The only usage signal is the parenthetical about read receipts, which is a behavior note rather than routing guidance.

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