Skip to main content
Glama

nylas

by io.usefulapi

List events

nylas_list_events
Read-only

List calendar events. Requires calendar_id (sent as a query param). Nylas v3: GET /v3/grants/{grant_id}/events.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endNoFilter: latest event start, Unix timestamp (seconds).
limitNoMax events to return.
startNoFilter: earliest event start, Unix timestamp (seconds).
grant_idNoConnected-account grant id. Overrides NYLAS_GRANT_ID for this call.
page_tokenNoPagination cursor (next_cursor from a prior page).
calendar_idYesREQUIRED. The calendar id (sent as a query param).
show_cancelledNoInclude cancelled events.

Schema Changelog

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

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true. The description adds the API endpoint but does not disclose pagination behavior, rate limits, or what happens with large date ranges. Minimal added value beyond annotations.

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 short sentences with front-loaded purpose. No wasted words. Efficiently conveys the core action and a key constraint.

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?

Given the complexity (7 parameters, no output schema), the description omits details about the returned data structure, pagination, and default behavior. An agent operating without additional context may not know how to interpret results.

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%, so the description's mention of calendar_id adds nothing beyond what the schema already provides. Baseline 3 applies.

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 calendar events' with specific resource and verb. The API endpoint reference adds context. Distinguishes from sibling tools like create, get, and other list operations.

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 guidance on when to use this tool versus alternatives (e.g., nylas_get_event for a single event). No mention of when not to use it or prerequisites beyond the required calendar_id.

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

All nylas toolsInspect
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.

TDQS

A3.7/5.0
Disambiguation5/5

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.

Resources