Skip to main content
Glama

graph_list_events

Lists calendar events for a date range or specified/shared calendar, supporting paging, filters, and compact results.

Instructions

List calendar events. Uses calendarView for date ranges, /events otherwise.

Args: start_datetime: Start of date range (ISO 8601, e.g. "2025-01-01T00:00:00Z"). Required with end_datetime for date range queries. end_datetime: End of date range (ISO 8601). Required with start_datetime. calendar_id: Optional calendar ID. Defaults to primary calendar. top: Maximum number of events to return (default 50). skip: Number of items to skip before returning results (default 0). Graph returns at most 50 per call, so page by raising skip in steps of top. filter_query: Optional OData filter (e.g. "isCancelled eq false"). Only applied on the /events path, because calendarView does not accept arbitrary filters. A filter on a recipient or organizer-style property also drops the sort, which Graph refuses to combine with it. compact: Whether to return only the identifying fields instead of the full record (default false). Use it to page through large collections cheaply. body_type: Body format to request: "html" or "text" (default "html"). Use "text" to avoid pulling large HTML bodies into context. next_link: Opaque nextLink URL from a previous call, used to fetch the next page. Overrides the other paging arguments when supplied. include_next_link: Whether to wrap the result as {items, next_link} so paging can continue (default false, which returns a bare list). user: Shared or delegated calendar owner address or user ID to act on. Empty targets your own calendar. Requires the delegated Calendars.Read.Shared or Calendars.ReadWrite.Shared permissions.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "graph_list_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNo
skipNo
userNo
compactNo
body_typeNohtml
next_linkNo
calendar_idNo
end_datetimeNo
filter_queryNo
start_datetimeNo
include_next_linkNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations supplied, the description carries the entire burden and does so well: it discloses Graph's 50-per-call cap and how to page, that filter_query is silently ignored on the calendarView path, that recipient/organizer filters drop the sort, that next_link overrides other paging args, and that the user parameter requires delegated Calendars.Read.Shared or ReadWrite.Shared permissions.

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?

Front-loaded one-line purpose followed by a structured Args block where nearly every line adds distinct operational value. Slightly dense, but there is no filler and no sentence that could be deleted without losing guidance.

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?

For an 11-parameter read tool with no annotations and no output schema, the description covers paging, result wrapping (bare list vs {items, next_link}), and payload size control. It is thinner on what an event record actually contains and says nothing about timezone handling or error behavior, but those are secondary for a listing call.

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

Parameters5/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 all 11 parameters, and it does: each arg gets type, default, format example, and interaction rules (start/end interdependence, next_link precedence, filter_query path restriction). This is meaning well beyond what the bare schema conveys.

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?

Opens with a specific verb and resource ("List calendar events") and even names the two underlying Graph endpoints used depending on input shape. It does not distinguish itself from the sibling graph_list_event_instances, so an agent must infer which of the two to pick for recurring-event expansions.

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 concrete conditional guidance: pair start_datetime with end_datetime for date-range queries, use the /events path when filtering, use compact for cheap paging, use body_type "text" to avoid large HTML payloads. It stops short of naming alternatives or stating when-not to use this tool versus sibling listing tools.

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