Skip to main content
Glama

Calendar: List events

calendar_list_events
Read-onlyIdempotent

List or search events inside one resolved calendar. Use this to obtain event.id before reading, updating or deleting an event. Google may read an accessible public calendar by ID even outside the private calendar list; Outlook stays account-bound.

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": {
      "calendar_id": "<calendar_id>"
    },
    "name": "calendar_list_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoISO 8601 upper time bound.
busyNo
limitNo
startNoISO 8601 lower time bound.
titleNo
cursorNo
offsetNo
ical_uidNo
locationNo
attendeesNo
account_idNoOptional Nilyo connection ID (unipile_account_id from list_connected_accounts). Omit when the user has one account for this provider. When several exist, Nilyo never guesses: list them (display name, identifier, provider user ID), choose the one the user named or ask, and pass its ID here.
event_typeNo
calendar_idYesExact calendar ID returned by calendar_list_calendars; never pass a calendar name. Calendar ID: Exact Google/Microsoft calendar id. Obtain with: calendar_list -> calendar.id Never pass: calendar display name.
descriptionNo
is_cancelledNo
updated_afterNo
updated_beforeNo
expand_recurringNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds value beyond that with provider-specific behavior: Google may resolve an accessible public calendar by ID even if it is absent from the private calendar list, while Outlook resolution stays account-bound — non-obvious scoping that affects whether a call succeeds. It says nothing about pagination behavior or how the many filters combine, which would have pushed this higher.

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?

Three sentences, front-loaded with the action and scope, then the workflow dependency, then the provider caveat — every sentence carries information. The final sentence is dense and reads slightly telegraphically ('Google may read an accessible public calendar by ID...'), but nothing is filler.

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 an 18-parameter tool with no output schema, the description covers the critical path (calendar resolution, id harvesting, provider differences) but leaves the search/filter semantics and pagination contract unexplained. An agent could call it correctly for the common case but would be guessing on the advanced filters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 22% across 18 parameters, so the description must compensate — and it largely does not. It reinforces calendar_id ('one resolved calendar') but never explains the semantics of the substantive filters (title, attendees, location, busy, is_cancelled, event_type, expand_recurring, updated_after/before) or whether they are substring/prefix/boolean-AND matches, and cursor/offset/limit pagination is unmentioned.

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 pair and resource: 'List or search events inside one resolved calendar.' The scoping phrase 'one resolved calendar' separates it from calendar-wide listing and from single-event operations, and the follow-on sentence clarifies its place in the read/update/delete workflow. It stops short of naming sibling tools like calendar_get_event explicitly, so an agent must infer the boundary.

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?

'Use this to obtain event.id before reading, updating or deleting an event' gives a concrete use context and downstream dependency, which is real routing guidance. It does not state when NOT to use it (e.g., when an event.id is already known and calendar_get_event would be cheaper), so it lacks explicit exclusions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.