Skip to main content
Glama
Sign In

mailbox.bot

by bot.mailbox
OverviewDiscussionsAdmin

list_inbound_items

Read-onlyIdempotent

Deprecated: use search_inbound_items. Still served unchanged during the alias window. Search managed-renter physical mail through GET /v1/inbound-items?search_mode=documents. q uses literal AND terms across authorized saved metadata, exterior OCR and completed requested inside-page OCR (NFKC/lowercase, max 200 characters and 12 terms). Terms may match different pages of one item. received_after is inclusive and received_before exclusive; these filter intake time, never a printed letter date. status and kind narrow canonical item metadata. Sender/address terms use q; identify them from actual page evidence, not guessed fields. Returns item metadata and canonical owner/mailbox identity, not page text. Use get_inbound_item_sources for selected items. Saved-data reads only: no extraction, retry, signed image URL, facility action, provider call, email or charge. Exterior automation and authorized inside-page extraction have independent activation; these readers do not enable either. Limit 1–50 (default 25), offset 0–10000; follow pagination.has_more using offset plus returned count, stop at the cap and narrow query/date windows or report incomplete history. Results are not snapshot-consistent. Bound concurrency, honor Retry-After when present, back off on transient failures, and stop on access errors. No new exterior-ready webhook or unbounded export is promised. Requires saved-document reads enabled for the account, an active eligible managed mailbox, and both inbound.item.read and inbound.item.scan.read, even for empty searches. Live member keys are owner-scoped; Live agent keys see only their current assigned mail. No facility, Sandbox or package.read compatibility access. Stop on denial; never switch keys, accounts or mail APIs to bypass it. A member key cannot select agent duties; use get_mailbox_md separately with the intended agent's agent.read scope.

Input Schema

NameRequiredDescriptionDefault
qNoLiteral AND search of authorized saved metadata and OCR; NFKC/lowercase, at most 200 characters and 12 terms. No fuzzy search or new extraction.
kindNoOnly items of this kind.
limitNoPage size, 1–50 (default 25).
offsetNoItems to skip, 0–10000 (default 0). Advance by the number returned while more remain; results are a current view, not a snapshot.
statusNoOnly items in this custody status.
received_afterNoInclusive canonical intake time (RFC3339 with timezone, up to six fractional-second digits); not a date printed in a letter.
received_beforeNoExclusive canonical intake time (RFC3339 with timezone, up to six fractional-second digits); not a date inferred from OCR.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / kind / description
      Added value: +"Only items of this kind."
    • addedInput schema / properties / limit / description
      Added value: +"Page size, 1–50 (default 25)."
    • addedInput schema / properties / offset / description
      Added value: +"Items to skip, 0–10000 (default 0). Advance by the number returned while more remain; results are a current view, not a snapshot."
    • addedInput schema / properties / status / description
      Added value: +"Only items in this custody status."
  2. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, non-destructive, and non-open-world traits. The description adds substantial operational context beyond that: no extraction/retry/provider calls, independent activation of exterior/inside-page extraction, pagination behavior, non-snapshot consistency, concurrency/backoff/Retry-After guidance, and key scoping rules. No contradictions with annotations.

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

Conciseness2/5

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

The description is a dense wall of text far longer than needed for a deprecated alias. It repeats schema-level details (limit/offset, q constraints) and piles on warnings. While the deprecation notice is front-loaded, the overall size is not appropriately concise and many sentences could be trimmed or moved to external docs.

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 complexity, rich schema, annotations, and output schema, the description is highly complete. It covers auth scopes, key scoping, pagination, data freshness, failure handling, and limitations. Nothing critical for correct invocation appears missing.

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?

Schema coverage is 100%, so the schema already documents each parameter. The description adds useful meaning: q matches across metadata and multiple OCR layers and may hit different pages; received_after/before filter intake time not printed dates; sender/address should be identified from page evidence. These additions go beyond the schema, though some points are redundant.

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?

The description clearly states it is deprecated in favor of search_inbound_items and describes the tool as searching managed-renter physical mail via a specific endpoint. The verb+resource are identifiable, and it distinguishes itself from the named replacement sibling. However, the name says 'list' while the description uses 'search', which creates minor tension.

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

Usage Guidelines5/5

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

Explicitly tells the agent to use search_inbound_items instead, notes this is only for the alias window, names get_inbound_item_sources for selected items, and lists prerequisites (saved-document reads enabled, eligible managed mailbox, required scopes). It also states exclusions (no facility/Sandbox/package.read) and denial handling.

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

All mailbox.bot toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources