Skip to main content
Glama
NexBrowser MCP Server

NexBrowser MCP Server

Official
by nex-browser

nex_mail_message_list

List and sync paginated email messages for a local mailbox ID, with keyword filters and polling waits to catch verification mail sent after a resend.

Instructions

Sync and list email for a local mailbox id: 10 per page, keyword filters, and codes come from the full keyword (never keywordDisplay). waitSeconds 0 syncs once; use 180 to wait for verification mail (polls every 10 seconds). receivedAfter (ISO time with timezone of the current send) ignores older mail; onlyNew ignores mail already present at the first sync, for use after a resend. Still match recipient and site. A confirmed empty wait returns MAIL_MESSAGE_TIMEOUT. At most 5 read calls per 3 seconds.

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": {
      "id": "<id>"
    },
    "name": "nex_mail_message_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
pageNo
keywordNo
onlyNewNo
waitSecondsNo
receivedAfterNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2026.11.3
    • changedInput schema / properties / receivedAfter / pattern
      Previous value: -"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$"New value: +"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$"
  2. Addedv2026.10.24

TDQS

A4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false, so the description carries most of the burden and does it well: it discloses the 10-second internal polling cadence, the MAIL_MESSAGE_TIMEOUT outcome of a confirmed empty wait, and a rate limit of 5 read calls per 3 seconds. What it omits is the side effect of 'sync' itself — whether mail is persisted locally, and what happens to mail already synced.

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?

Dense and front-loaded — the core action and pagination come first, then per-parameter behavior, then the error code and rate limit. The telegraphic fragments ('Still match recipient and site', 'never keywordDisplay') cost some readability without much wasted length.

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

Completeness4/5

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

With no output schema, 6 parameters and 0% schema coverage, the definition does most of the heavy lifting an agent needs to call it correctly. Remaining gaps are where the mailbox id comes from and what the returned list looks like, both of which would matter for a first-time caller.

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 description coverage is 0%, so the description must define meaning and it covers most parameters: waitSeconds semantics and polling, receivedAfter's ISO/timezone convention, onlyNew's baseline ('mail already present at the first sync'), and the keyword/code-matching rule. 'page' is only implied by '10 per page' and the mailbox 'id' origin is not explained, leaving two gaps.

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 concrete verb pair ('Sync and list') and resource ('email for a local mailbox id'), plus pagination size of 10 per page, so the agent knows this retrieves mail rather than inspecting a single message like the sibling nex_mail_message_detail. It never names that sibling explicitly, so differentiation relies on the reader inferring 'list' vs 'detail'.

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?

Gives strong conditional guidance: waitSeconds 0 syncs once, 180 waits for verification mail; onlyNew is for use after a resend; receivedAfter ignores older mail. It does not name an alternative tool to use instead in any scenario, so it stops short of full when/when-not routing.

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