mailwarden

mark_read

Idempotent

Mark one or up to 100 Gmail threads as read in a single call, with per-thread results for changed, failed, and notAttempted threads; revert with mark_unread.

Instructions

Mark a thread as read. Pass threadIds (a list of up to 100) instead of threadId to apply the same change to every listed thread in one call — for 'exactly these threads, as approved'. The answer then reports per thread: changed, failed (with code and message; the others still ran) and notAttempted (the run stopped at a rate limit, dead token or missing scope, which would have hit every remaining thread alike); ok is true only when all were changed. SIDE EFFECTS: removes UNREAD; reversible via mark_unread.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "mark_read"
  }
}

Input Schema

Name	Required	Description	Default
`threadId`	No
`threadIds`	No

Output Schema

Name	Required	Description	Default
`ok`	Yes
`failed`	No
`changed`	No
`notAttempted`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv0.25.0Oct 29, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

addedInput schema / properties / threadIds

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "minItems": 1,
+  "type": "array"
+}

removedInput schema / required
```
Removed value: -[
-  "threadId"
-]
```

addedOutput schema / properties / changed

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / failed

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "code": {
+        "type": "string"
+      },
+      "message": {
+        "type": "string"
+      },
+      "retryable": {
+        "type": "boolean"
+      },
+      "threadId": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "threadId",
+      "code",
+      "message",
+      "retryable"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / notAttempted

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

First observedv0.1.8Jul 24, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the annotations, the description discloses side effects ('removes UNREAD'), reversibility via `mark_unread`, partial-success behavior, per-thread failure reporting, and the meaning of `ok`. It also explains that `notAttempted` is caused by run-stopping conditions like rate limits, dead tokens, or missing scope, which is unusually rich behavioral context.

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 description is front-loaded with the core action and batch guidance, then proceeds to result semantics and side effects. It is dense and slightly long, but each sentence adds useful operational detail rather than repeating structured fields.

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?

Given the existence of an output schema, the description need not document return shape in full, yet it still summarizes key result fields. It covers the important mutation behavior, reversibility, batch limits, and partial-failure cases sufficiently for an agent to call the tool correctly.

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

Parameters4/5

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

With 0% schema description coverage, the description carries the burden well: it explains that `threadIds` is a list of up to 100 and is an alternative to `threadId` for batch application. It does not specify ID format or what happens if both parameters are supplied, but the core semantics are clear.

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 states a specific verb and resource ('Mark a thread as read') and immediately clarifies the batch variant via `threadIds`. It distinguishes the operation from its reversible counterpart `mark_unread` and from single-thread usage without requiring the schema.

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

Usage Guidelines4/5

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

It explicitly instructs using `threadIds` instead of `threadId` for applying the change to every listed thread in one call. The use case is clear, though it does not spell out when not to use the tool or when to prefer a single-thread call beyond the parameter distinction.

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