nylas

List messages

nylas_list_messages

Read-only

List email messages for the connected account, with optional filters. Nylas v3: GET /v3/grants/{grant_id}/messages.

Input Schema

TableJSON Schema

Name	Required	Description
`in`	No	Filter by folder id.
`to`	No	Filter by recipient email address.
`from`	No	Filter by sender email address.
`limit`	No	Max messages to return.
`unread`	No	If set, filter by unread status.
`starred`	No	If set, filter by starred status.
`subject`	No	Filter by subject.
`grant_id`	No	Connected-account grant id. Overrides NYLAS_GRANT_ID for this call.
`page_token`	No	Pagination cursor (next_cursor from a prior page).
`search_query_native`	No	Provider-native search query string.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedJul 18, 2026

TDQS

A3.5/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, so safety is covered. Description adds endpoint info but no behavioral details like pagination or rate limits beyond what the schema provides.

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

Conciseness5/5

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

Two sentences, front-loaded with purpose, no wasted words.

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?

Adequate for a listing tool with many filters, but lacks explanation of pagination behavior or response structure. No output schema, so a bit more context would help.

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% with clear descriptions for all 10 parameters. The tool description adds no additional meaning over the schema.

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?

Clearly states 'List email messages' with verb and resource, and distinguishes from siblings like nylas_get_message and nylas_list_drafts via context.

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?

Implies usage for listing messages with optional filters, but no explicit guidance on when not to use or alternatives like search.

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

All nylas tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Each tool targets a distinct resource and action: create vs list vs get for specific entities like draft, event, calendar, contact, grant, message, folder. There is no overlap, as even similar verbs like 'list' are paired with unique nouns. Agents can easily select the correct tool.

Naming Consistency5/5

All tool names follow a uniform 'nylas_verb_noun' pattern using snake_case, with clear and predictable verbs (create, get, list, send) and nouns (draft, event, calendar, etc.). The naming is fully consistent across all 15 tools.

Tool Count5/5

With 15 tools, the set is well-scoped for a Nylas integration covering email, calendar, and contacts. Each tool serves a clear purpose without redundancy, and the count falls comfortably within the ideal range of 3-15 tools.

Completeness3/5

The tool set covers reading and limited creation (drafts, events) but lacks update and delete operations for all entities, as well as create for contacts. This leaves notable gaps for full lifecycle management, though core workflows like listing and fetching are present.

List messages

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources