Skip to main content
Glama
Sign In
privateemail-mcp

privateemail-mcp

by pushkarsingh32
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

mark_read

Mark specified email messages as read or unread by UID in a chosen mailbox folder, such as INBOX or Sent, to keep message status accurate.

Instructions

Mark messages as read or unread.

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": {
      "uids": "<uids>"
    },
    "name": "mark_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
readNo
uidsYes
folderNoMailbox folder path, e.g. INBOX or SentINBOX

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. For a mutation tool it says nothing about whether the operation is idempotent, what permissions or folder access are required, that it is capped at 100 UIDs per call, or what happens to already-read messages.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single efficient sentence with no waste and the action front-loaded. However, the brevity reflects under-specification rather than disciplined concision given the gaps in behavior and parameters.

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

Completeness2/5

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

A mutation tool with no annotations, no output schema, and three parameters at 33% schema coverage. The description should compensate by explaining UID semantics, the read/unread toggle, and folder targeting, but it does none of that.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 33% (only 'folder' is documented in the schema). The description adds no meaning for 'uids' (a bounded array of mailbox UIDs, max 100) or the 'read' boolean, whose semantics — and the fact that it defaults to true — are left entirely to the schema's type info.

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 and resource ('mark messages') plus the toggle ('as read or unread'), which is clearer than the bare name mark_read. It is distinguishable from siblings like read_message or move_messages, though it never explicitly contrasts with them.

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 guidance on when to use this versus read_message (which presumably also marks read) or move_messages. It implies a bulk-flagging operation but never states prerequisites, scope, or when not to use it.

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