Skip to main content
Glama
AgenticMail

AgenticMail

Official
by agenticmail

batch_mark_unread

Mark multiple emails as unread by passing their UIDs, with an optional folder and INBOX default, to bulk update read status.

Instructions

Mark multiple emails as 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": "batch_mark_unread"
  }
}

Input Schema

NameRequiredDescriptionDefault
uidsYesArray of UIDs to mark as unread
folderNoFolder (default: INBOX)
_accountNoOptional. Override identity for THIS call: pass the AgenticMail agent name (e.g. "Fola") to authenticate as that agent. Requires AGENTICMAIL_ACCOUNT_KEYS_JSON to contain a matching key. Omit to use the default identity (AGENTICMAIL_API_KEY).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.9.104
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Addedv0.9.101
  3. Removedv0.9.89
  4. Addedv0.9.73
  5. Removedv0.9.69
  6. Addedv0.9.35
  7. Removedv0.9.31
  8. Addedv0.9.12
  9. Removedv0.9.11
  10. Changed1 schema field changedv0.5.63
    • addedInput schema / properties / _account
      Added value: +{
      +  "description": "Optional. Override identity for THIS call: pass the AgenticMail agent name (e.g. \"Fola\") to authenticate as that agent. Requires AGENTICMAIL_ACCOUNT_KEYS_JSON to contain a matching key. Omit to use the default identity (AGENTICMAIL_API_KEY).",
      +  "type": "string"
      +}
  11. First observedv0.5.59

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden and delivers only a restatement of the operation. It does not disclose whether the change is reversible, what happens when a UID does not exist or is in another folder, whether the call is partial-success or atomic, or whether account-level auth (_account) is required.

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?

A single front-loaded sentence with zero filler, but the terseness comes at the cost of substance rather than being a tight, complete statement.

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?

For a 3-parameter mutation tool with no annotations and no output schema, the description should at minimum say what the call returns (e.g., count of UIDs updated) and address partial failure. Neither is covered, leaving the agent to guess at outcomes.

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 description coverage is 100%, so uids, folder, and _account are already documented in structured data. The description adds no meaning beyond that, which matches the baseline 3 for full schema coverage.

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 (mark as unread) and resource (multiple emails), making the batch nature explicit via 'multiple'. It gives no differentiation from siblings like batch_mark_read or mark_unread, so the agent must infer the distinction from the names alone.

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 at all: the description never says when to prefer this over mark_unread (single) or how it relates to batch_mark_read. The list-of-uids vs single-uid distinction is only inferable from the schema, not the prose.

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