Skip to main content
Glama
AgenticMail

AgenticMail

Official
by agenticmail

batch_read

Read multiple emails by UID in one call and return fully parsed content for each message, reducing repeated requests when processing several emails at once.

Instructions

Read multiple emails at once by UIDs. Returns full parsed content for each message in a single call.

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_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
uidsYesArray of UIDs to read
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

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does add real value by stating the return is "full parsed content for each message in a single call," but it omits important behavior: whether reading marks messages as read (relevant given separate batch_mark_read tools exist), how failures on individual UIDs are handled, and any size or rate limits on the batch.

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?

Two tight sentences with the core purpose and the return shape front-loaded; nothing is redundant. Slightly more compact framing of the batching aspect could tighten it further, but the wording is efficient.

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

Completeness3/5

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

For a three-parameter read tool with no annotations and no output schema, the description covers what comes back at a high level. It leaves the agent without an answer to the highest-risk question for a read tool in a mail system — whether messages are marked read — and without any batch-size or partial-failure guidance.

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%, including a long self-explanatory _account parameter, so the baseline is 3. The description only reinforces that uids are the primary key and adds no semantics about ordering of results, folder scoping interactions, or UID validity beyond what the schema already documents.

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 ("Read multiple emails") plus the keying mechanism (UIDs) and the batch scope, which naturally separates it from the single-message read_email. It stops short of explicitly naming an alternative, but the "multiple... at once" framing makes the distinction clear.

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?

Usage is only implied: the agent can infer this is the bulk variant and appropriate when several UIDs are known. There is no explicit when-to-use/when-not guidance, no mention of the single-read alternative, and no note on limits (max UIDs, error behavior if one UID is invalid).

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